[opensourcedex]

HyperDX is a free, open source monitoring & observability project written in TypeScript and released under MIT. It has 9,897 GitHub stars, 469 forks and 187 open issues, and was last pushed 5 hours ago. On this registry it ranks #46 of 97 tracked projects in Monitoring & Observability, with 5 head-to-head comparisons available. It gained 12 stars over the last 6 tracked days.

What is HyperDX?

What it is

HyperDX is an open-source observability platform that unifies session replays, logs, metrics, traces, and errors. It is built on ClickHouse and OpenTelemetry, and it is positioned as a core component of ClickStack. The project lives in the open-source infrastructure and operations ecosystem, especially around log management, application monitoring, frontend monitoring, Kubernetes, and APM.

The problem it solves is slow production debugging when telemetry is split across tools, schemas, and vendors. HyperDX lets engineers search and visualize logs and traces on top of an existing ClickHouse cluster, so they can correlate events and identify why production is broken. It also supports schema-agnostic operation on existing ClickHouse schemas, reducing the need to rebuild a data model first.

Key capabilities

  • HyperDX correlates and searches logs, metrics, session replays, and traces in one place.
  • It supports full-text search and property search syntax, such as level:err, with SQL optional.
  • It analyzes anomaly trends with event deltas and lets users set up alerts from the interface.
  • It provides dashboards for high-cardinality events, native JSON string querying, and live tailing for logs and traces.
  • It supports OpenTelemetry out of the box and monitors application health and performance from HTTP requests to database queries.
  • It provides a CLI and interactive TUI for search, live tail, trace waterfalls, dashboard tiles, raw SQL queries, NDJSON output, and Drain log pattern mining.

Who uses it and how

  • Platform teams use HyperDX as the UI and search layer for logs and traces stored in ClickHouse.
  • Application teams instrument services with Browser, Node.js, Python, or OpenTelemetry SDKs, then send telemetry to HyperDX.
  • Kubernetes operators deploy HyperDX as part of ClickStack with ClickHouse, HyperDX, OpenTelemetry Collector, and MongoDB.
  • Engineers use the CLI to search data, live tail logs, inspect trace waterfalls, render dashboard tiles, or run scripted queries.

Getting started

Typical deployment uses the Docker image docker.hyperdx.io/hyperdx/hyperdx-all-in-one, exposes port 8080 for the UI, and points applications to the OpenTelemetry collector on port 4318. The CLI can be installed with npm install -g @hyperdx/cli, and a hosted option is available through ClickHouse Cloud.

When to use it — and when not to

HyperDX is useful when an organization already uses ClickHouse and wants a Kibana-like search and visualization experience for logs, traces, metrics, session replays, and alerts. Self-hosters must operate ClickHouse, the HyperDX application, an OpenTelemetry collector, and MongoDB when using ClickStack, and they must manage firewall ports for the UI, API, and collector. The project appears young, with repository metadata showing zero contributors and many open issues, so teams needing mature vendor support may prefer a more established platform.

project readme (upstream, from github) — read inline

HyperDX

GitHub stars License Release Join the HyperDX Discord

hyperdxio%2Fhyperdx | Trendshift

HyperDX, a core component of ClickStack, helps engineers quickly figure out why production is broken by making it easy to search & visualize logs and traces on top of any ClickHouse cluster (imagine Kibana, for ClickHouse).

Documentation • Chat on Discord • Live Demo • Bug Reports • Contributing • Website

  • 🕵️ Correlate/search logs, metrics, session replays and traces all in one place
  • 📝 Schema agnostic, works on top of your existing ClickHouse schema
  • 🔥 Blazing fast searches & visualizations optimized for ClickHouse
  • 🔍 Intuitive full-text search and property search syntax (ex. level:err), SQL optional!
  • 📊 Analyze trends in anomalies with event deltas
  • 🔔 Set up alerts in just a few clicks
  • 📈 Dashboard high cardinality events without a complex query language
  • { Native JSON string querying
  • ⚡ Live tail logs and traces to always get the freshest events
  • 🔭 OpenTelemetry supported out of the box
  • ⏱️ Monitor health and performance from HTTP requests to DB queries (APM)

Spinning Up HyperDX

HyperDX can be deployed as part of ClickStack, which includes ClickHouse, HyperDX, OpenTelemetry Collector and MongoDB.

docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one

Afterwards, you can visit http://localhost:8080 to access the HyperDX UI.

If you already have an existing ClickHouse instance, want to use a single container locally, or are looking for production deployment instructions, you can view the different deployment options in our deployment docs.

If your server is behind a firewall, you'll need to open/forward port 8080, 8000 and 4318 on your firewall for the UI, API and OTel collector respectively.

We recommend at least 4GB of RAM and 2 cores for testing.

Hosted ClickHouse Cloud

You can also deploy HyperDX with ClickHouse Cloud, you can sign up for free and get started in just minutes.

Instrumenting Your App

To get logs, metrics, traces, session replay, etc into HyperDX, you'll need to instrument your app to collect and send telemetry data over to your HyperDX instance.

We provide a set of SDKs and integration options to make it easier to get started with HyperDX, such as Browser, Node.js, and Python

You can find the full list in our docs.

OpenTelemetry

Additionally, HyperDX is compatible with OpenTelemetry, a vendor-neutral standard for instrumenting your application backed by CNCF. Supported languages/platforms include:

  • Kubernetes
  • Javascript
  • Python
  • Java
  • Go
  • Ruby
  • PHP
  • .NET
  • Elixir
  • Rust

(Full list here)

Once HyperDX is running, you can point your OpenTelemetry SDK to the OpenTelemetry collector spun up at http://localhost:4318.

HyperDX CLI

Prefer the terminal? @hyperdx/cli provides an interactive TUI and CLI (hdx) for working with your HyperDX data without leaving the shell:

npm install -g @hyperdx/cli
hdx auth login
hdx tui
  • 🖥️ Interactive TUI — search, live tail, and trace waterfalls with vim-style keybindings
  • 📊 Render dashboard tiles and ad-hoc charts as ANSI output in the terminal
  • 🤖 Agent-friendly: raw SQL queries, NDJSON output, and Drain log pattern mining for scripts and AI agents

See the CLI README for the full command reference.

Contributing

We welcome all contributions! There's many ways to contribute to the project, including but not limited to:

Pull requests. Issues, bug reports and discussion stay open to everyone. For code we now use Vouch: a maintainer has to vouch for you before your first pull request gets reviewed. AI tools make it cheap to open a plausible-looking PR with no understanding behind it, and reviewing those crowds out the contributions we want to spend time on. Getting vouched takes one issue — say hello and tell us what you want to work on. See Getting vouched.

Motivation

Our mission is to help engineers ship reliable software. To enable that, we believe every engineer needs to be able to easily leverage production telemetry to quickly solve burning production issues.

However, in our experience, the existing tools we've used tend to fall short in a few ways:

  1. They're expensive, and the pricing has failed to scale with TBs of telemetry becoming the norm, leading to teams aggressively cutting the amount of data they can collect.
  2. They're hard to use, requiring full-time SREs to set up, and domain experts to use confidently.
  3. They requiring hopping from tool to tool (logs, session replay, APM, exceptions, etc.) to stitch together the clues yourself.

We hope you give HyperDX in ClickStack a try and let us know how we're doing!

Contact

HyperDX Usage Data

HyperDX collects anonymized usage data for open source deployments. This data supports our mission for observability to be available to any team and helps support our open source product run in a variety of different environments. While we hope you will continue to support our mission in this way, you may opt out of usage data collection by setting the USAGE_STATS_ENABLED environment variable to false. Thank you for supporting the development of HyperDX!

License

MIT

Frequently asked questions

Is HyperDX free to use?

HyperDX is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does HyperDX do?

Full-stack observability without the enterprise price tag

What is HyperDX written in?

HyperDX is primarily written in TypeScript. Its source is publicly available at https://github.com/hyperdxio/hyperdx, and it has 9,897 GitHub stars.