Better Stack (Log Management)
Cloud-based log management solution for aggregating, searching, and analyzing application logs at scale
HyperDX
ClickHouse-native observability platform unifying logs, traces, and replays
HyperDX delivers fast, unified observability on ClickHouse. Search logs, traces, metrics, and session replays in one interface—no complex query language required.
Overview
Modern Observability Built for ClickHouse
HyperDX is an observability platform that helps engineers diagnose production issues by unifying logs, traces, metrics, and session replays on top of ClickHouse. Designed as a core component of ClickStack, it brings Kibana-like search and visualization capabilities optimized for ClickHouse's columnar architecture.
Schema-Agnostic and Developer-Friendly
Unlike traditional observability tools that require expensive proprietary backends, HyperDX works directly with your existing ClickHouse schema. Engineers can search telemetry using intuitive full-text and property syntax (level:err) without writing SQL, while still having the option to leverage ClickHouse's query power when needed. Native JSON querying, live tail, and high-cardinality dashboards make it easy to explore production data without specialized training.
OpenTelemetry-Native Integration
HyperDX supports OpenTelemetry out of the box, enabling instrumentation across JavaScript, Python, Java, Go, Ruby, PHP, .NET, and more. Deploy as a single Docker container for testing or integrate with ClickHouse Cloud for production workloads. The platform correlates data across telemetry types, helping teams move from symptom to root cause without tool-hopping.
Highlights
Unified search across logs, traces, metrics, and session replays in one interface
Schema-agnostic design works on top of existing ClickHouse clusters
Intuitive full-text and property search syntax with optional SQL queries
Native OpenTelemetry support with SDKs for Browser, Node.js, Python, and more
Pros
- Leverages ClickHouse for blazing fast searches and cost-effective storage
- No vendor lock-in; works with existing ClickHouse infrastructure
- Single-container deployment option simplifies local testing and development
- Correlates multiple telemetry types to accelerate root cause analysis
Considerations
- Requires ClickHouse expertise for production tuning and optimization
- Smaller ecosystem and community compared to established observability vendors
- MongoDB dependency adds operational complexity to the stack
- Limited documentation for advanced customization and enterprise features
Managed products teams compare with
When teams consider HyperDX, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Teams already running ClickHouse who want native observability tooling
- Engineering organizations seeking cost-effective alternatives to SaaS observability platforms
- DevOps teams needing unified telemetry correlation without tool sprawl
- OpenTelemetry adopters looking for a self-hosted backend with session replay
Not ideal when
- Organizations without ClickHouse experience or infrastructure
- Teams requiring enterprise support contracts and SLAs
- Small projects needing zero-configuration managed observability services
- Environments where adding MongoDB as a dependency is prohibitive
How teams use it
Correlating Frontend Errors with Backend Traces
Engineers replay user sessions to see JavaScript errors, then jump directly to related API traces and logs to identify the root cause in minutes instead of hours.
Cost-Effective Log Aggregation at Scale
Platform teams ingest terabytes of logs into ClickHouse and use HyperDX for fast full-text search and dashboards, reducing observability costs by 70% compared to SaaS vendors.
Kubernetes APM and Performance Monitoring
SREs instrument microservices with OpenTelemetry, then monitor HTTP request latency, database query performance, and distributed traces across the entire cluster from one dashboard.
Real-Time Production Debugging with Live Tail
On-call engineers use live tail to stream logs and traces during incidents, spotting anomalies and setting up alerts in just a few clicks without writing complex queries.
Tech snapshot
TypeScript95%
SCSS2%
Shell1%
JavaScript1%
Dockerfile1%
Makefile1%
Frequently asked questions
Does HyperDX require an existing ClickHouse cluster?
No. The all-in-one Docker container includes ClickHouse, HyperDX, OpenTelemetry Collector, and MongoDB. For production, you can connect to an existing ClickHouse instance or use ClickHouse Cloud.
What are the minimum system requirements for testing HyperDX?
At least 4GB of RAM and 2 CPU cores are recommended for local testing. Production deployments should be sized based on telemetry volume and query load.
Can I use HyperDX without writing SQL queries?
Yes. HyperDX provides intuitive full-text and property search syntax (e.g., level:err) for common use cases. SQL is optional for advanced queries leveraging ClickHouse's full power.
Does HyperDX collect telemetry about my deployment?
HyperDX collects anonymized usage data by default to support development. You can opt out by setting the USAGE_STATS_ENABLED environment variable to false.
Project at a glance
Active- Stars
- 9,257
- Watchers
- 9,257
- Forks
- 353
LicenseMIT
Repo age2 years old
Last commit4 hours ago
Self-hostingSupported
Primary languageTypeScript
Last synced 2 hours ago