What is HyperDX?
HyperDX is a core component of ClickStack that helps engineers investigate production issues using logs, metrics, traces, errors and session replays. It works with existing ClickHouse schemas and provides full-text and property-based search, native JSON string querying and optional SQL. Engineers can follow incoming logs and traces with live tail, compare event properties to investigate anomalies and monitor application performance from HTTP requests to database queries.
HyperDX can be self-hosted in containers as part of ClickStack, alongside ClickHouse, an OpenTelemetry Collector and MongoDB, or deployed with ClickHouse Cloud. Applications must be instrumented to send telemetry through supported SDKs or OpenTelemetry. A companion CLI provides terminal access, while an authenticated MCP server exposes data exploration and dashboard management to compatible AI clients on supported self-hosted deployments.
HyperDX screenshots
Explore the interface. Open a screenshot to view it at full size.
Source: official HyperDX project page.
Key capabilities
- Search across logs, metrics, session replays and traces
- Works on your existing ClickHouse schema
- Alerts and dashboards for high-cardinality events
- Live tail of logs and traces
- APM views for HTTP requests and database queries
- OpenTelemetry support and SDKs for browser, Node.js and Python
- An interactive TUI and CLI (hdx)
Where HyperDX fits
HyperDX fits production incident investigation and application performance analysis, particularly where teams already store telemetry in ClickHouse or use OpenTelemetry instrumentation. Engineers can move between browser session context, application logs and distributed traces, then capture recurring investigations in saved searches, dashboards and alerts. Before deployment, teams should verify instrumentation coverage, ClickHouse connectivity, resource requirements and network access for the interface, API and collector.
Its MCP server supports assistant-driven telemetry queries and management of dashboards, sources and alerts. Deployment checks should include personal API key handling and the scope of permitted changes, since some tools can permanently delete resources. MCP support applies to self-hosted HyperDX v2 Free and Enterprise, not HyperDX v1. Open-source deployments also collect anonymized usage data unless collection is disabled through configuration.
Install
docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-oneReviews of HyperDX
Be the first to share your experience with HyperDX.
Write a review
Loading review form…

