An OTel-native observability stack on open backends — VictoriaMetrics for hot operational metrics, ClickHouse for long-term analytical intelligence — unified into one dashboard surface covering all four FalconIO features. No proprietary lock-in. No per-host pricing.
VictoriaMetrics handles your operational hot path. ClickHouse handles your analytical depth. They are complementary — each does precisely what the other cannot. Running both is a deliberate architectural decision, not an oversight.
One dashboard surface for all four FalconIO features. IDP request state, infra topology, operational telemetry, BC Manifest coverage, incident queue — no context-switching between tools.
Distributed traces stored in ClickHouse alongside infrastructure metrics. Correlate a service latency spike with a CockroachDB replica lag event in a single query. Performance as a consequence of infrastructure state.
Long-term ClickHouse aggregations on CPU, memory, GPU, network, and storage by workload, namespace, and environment tier. Understand patterns, not just current utilisation.
Autoscaling parameters informed by ClickHouse demand analytics — baseline profiles and burst distributions derived from historical data. AI-assisted recommendation available. Full manual control with analytical visibility if preferred.
Pre-built for SCM, logistics, manufacturing, and industrial stacks. Kafka/Redpanda lag, CockroachDB replication lag, order pipeline velocity, warehouse throughput — correlated with infrastructure state. Not generic cluster health.
Observability is the source of truth for BC/DR trigger thresholds and incident context. When an alert fires, the incident ticket is created with the triggering metric, historical baseline, and affected services — automatically, before an engineer touches a keyboard.
We do not lead with cost. We lead with resilience, analytical depth, and operational intelligence. The 60–80% cost reduction vs Datadog at comparable telemetry volumes is a consequence of choosing open backends with no per-host, per-metric, or per-user pricing.
For enterprises running hundreds of Kubernetes nodes across US and European production environments, that consequence is material. It is also irreversible — once you own your telemetry data and the query infrastructure to analyse it, there is no reason to go back.