How observexinc/observex_managed works
ObserveX Managed is a self-hosted observability platform. Its main collection path runs from host agents through a Unified Gateway to Server intake and the configured stores; operators explore results in the web Console. The README also documents node supervision, a TLS Front Door, self-monitoring, browser telemetry, and six store types. Some feature modules are present in the tree but their wiring was not sampled, so those relationships are left unasserted or marked unverified.
Main entry points: server.go ObserveX Server · gateway.go Unified Gateway · supervisor.go Node Supervisor · agent.go Host Agent
Components 22
Telemetry Collection
- Host Agent
internal/agent/agent.go - Unified Gateway
internal/gateway/gateway.go - Browser Collector
web/console/browser/src/collect.ts
Node Platform
- Node Supervisor
internal/node/supervisor/supervisor.go - NGINX Front Door
internal/node/frontdoor/frontdoor.go - Node Self-Monitoring
internal/node/selfmon/selfmon.go
Server Services
- ObserveX Server
internal/server/server.go - Telemetry Intake
internal/server/intake/intake.go - Signal Pipeline
internal/server/pipeline/pipeline.go - Entity Graph
internal/server/graph/service.go - Investigator
internal/server/investigator/tools.go - Proof Chain
internal/server/proofchain/block.go - Public API
internal/server/api/server.go
State Stores
- MetricStore
internal/store/cassandra/metric.go - SearchStore
internal/store/opensearch/search.go - TraceStore
internal/store/tracestore/store.go - ConfigurationStore
internal/store/etcdstore/store.go
Web Console
- Console Application
web/console/src/App.tsx - Console API Client
web/console/src/api.ts - Observability Views
web/console/src/pages/Entities.tsx
Other components
- Monitored Host
- Operator
Connections 21
- Monitored Host → Host Agent: runs on
- Host Agent → Unified Gateway: forwards telemetry
- Unified Gateway → Telemetry Intake: delivers batches
- ObserveX Server → Telemetry Intake: starts
- ObserveX Server → Public API: starts
internal/server/server.go - ObserveX Server → MetricStore: configures stores
- ObserveX Server → SearchStore: configures stores
- ObserveX Server → TraceStore: configures stores
- ObserveX Server → ConfigurationStore: configures stores
- ObserveX Server → Signal Pipeline: runs
- ObserveX Server → Entity Graph: runs
- ObserveX Server → Investigator: runs
- ObserveX Server → Proof Chain: runs
- Node Supervisor → NGINX Front Door: starts
- Node Supervisor → ObserveX Server: starts
- Operator → Console Application: uses
- Console Application → Observability Views: routes to
web/console/src/App.tsx - Observability Views → Console API Client: requests data
web/console/src/pages/Entities.tsx - Console API Client → Public API: calls over HTTP
- Browser Collector → Unified Gateway: sends telemetry
- ObserveX Server → Node Self-Monitoring: registers metrics
internal/server/server.go