HyperDX

HyperDX helps engineers work out why production broke by making logs and traces searchable on top of any ClickHouse cluster. Think of it as Kibana pointed at ClickHouse, and it reads whatever schema is already there instead of demanding a new one.

It is a core component of ClickStack, which bundles ClickHouse, HyperDX, an OpenTelemetry collector, and MongoDB. One Docker command brings the whole set up and serves the interface on port 8080, while teams with an existing ClickHouse instance or a ClickHouse Cloud account can point HyperDX at that instead.

Searching is built for people who do not want to write SQL under pressure.

• Property search: full-text search alongside a short property syntax such as level:err, with SQL optional.
• Correlated signals: logs, metrics, session replays, and traces are searched and viewed in one place.
• Live tail: logs and traces stream in, so the freshest events are always on screen.
• Event deltas: anomalies are compared against normal traffic to show what actually changed.
• Alerts and dashboards: alerts take a few clicks, and high cardinality events chart without a query language.
• Terminal client: an hdx CLI offers a TUI with vim-style keys, ANSI charts, NDJSON output, and Drain pattern mining.

Instrumentation goes through OpenTelemetry, covering Kubernetes, JavaScript, Python, Java, Go, Ruby, PHP, .NET, Elixir, and Rust, with the collector listening on port 4318. Testing wants at least 4 GB of RAM and two cores. Code contributions now use a vouching model, where a maintainer sponsors a newcomer before a first pull request is reviewed.