7 ms·
Show HN: ClickStack – Open-source Datadog alternative by ClickHouse and HyperDX
Hey HN! Mike & Warren here from HyperDX (now part of ClickHouse)! We’ve been building ClickStack, an open source observability stack that helps you collect, centralize, search/viz/alert on your telemetry (logs, metrics, traces) in just a few minutes - all powered by ClickHouse (Apache2) for storage, HyperDX (MIT) for visualization and OpenTelemetry (Apache2) for ingestion.
You can check out the quick start for spinning things up in the repo here: https://github.com/hyperdxio/hyperdx https://github.com/hyperdxio/hyperdx
ClickStack makes it really easy to instrument your application so you can go from bug reports of “my checkout didn’t go through” to a session replay of the user, backend API calls, to DB queries and infrastructure metrics related to that specific request in a single view.
For those that might be migrating from Very Expensive Observability Vendor (TM) to something open source, more performant, and doesn’t require extensive culling of retention limits and sampling rates - ClickStack gives a batteries-included way of starting that migration journey.
For those that aren’t familiar with ClickHouse, it’s a high performance database that has already been used by companies such as Anthropic, Cloudflare, and DoorDash to power their core observability at scale due to its flexibility, ease of use, and cost effectiveness. However, this required teams to dedicate engineers to building a custom observability stack, where it’s difficult to not only get their telemetry data easily into ClickHouse but also struggling without a native UI experience.
That’s why we’re building ClickStack - we wanted to bundle an easy way to get started ingesting your telemetry data whether it’s logs & traces from Node.js or Ruby to metrics from Kubernetes or your bare metal infrastructure. Just as important we wanted our users to enjoy a visualization experience that allowed users to quickly search using a familiar lucene-like search syntax (similar to what you’d use in Google!). We recognise though, that a SQL mode is needed for the most complex of queries. We've also added high cardinality outlier analysis by charting the delta between outlier and inlier events - which we've found really helpful in narrowing down causes of regressions/anomalies in our traces as well as log patterns to condense down clusters of similar logs.
We’re really excited about the roadmap ahead in terms of improving ClickStack as a product and the ClickHouse core database to improve observability. Would love to hear everyone’s feedback and what they think!
Spinning up a container is pretty simple: `docker run -p 8080:8080 -p 4317:4317 -p 4318:4318 docker.hyperdx.io/hyperdx/hyperdx-all-in-one`
In browser live demo (no sign ups or anything silly, it runs fully in your browser!): https://play.hyperdx.io/ https://play.hyperdx.io/ Landing Page: https://clickhouse.com/o11y https://clickhouse.com/o11y Github Repo: https://github.com/hyperdxio/hyperdx https://github.com/hyperdxio/hyperdx
Discord community: https://hyperdx.io/discord https://hyperdx.io/discord
Docs: https://clickhouse.com/docs/use-cases/observability/clickstack/getting-started https://clickhouse.com/docs/use-cases/observability/clicksta...
- readdit 1y agoI like and use HyperDX in production and like it a lot. So kudos to the team for building and merging with Clickhouse. I found a lot of monetary value switching over to HyperDX considering it's significantly more cost efficient for our needs. Should we be starting to prepare for the original HyperDX product to be deprecated and potentially move over to ClickStack?
- mikeshi42 1y agoFirst off, always really excited to hear from our production users - glad to hear you're getting good value out of the platform! HyperDX isn't being deprecated, you can probably see on the marketing page it's still really prominently featured as an integral part of the stack - so nothing changing there. We do of course want to get users onto HyperDX v2 and the overall ClickStack pattern. This doesn't mean HyperDX is going away by any means - just that HyperDX is focused a lot more on the end-user experience, and we get to leverage the flexibility, learnings and performance of a more exposed ClickHouse-powered core which is the intent of ClickStack. On the engineering side, we're working on making sure it's a smooth path for both open source and cloud. side note: weird I thought I replied to this one already but I've been dealing with spotty wifi today :)
- HatchedLake721 1y agoStill confused where HyperDX ends and where ClickStack starts. Is HyperDX === ClickStack? Is ClickStack = HyperDX + something closed source? Is ClickStack just a cloud version of HyperDX? Is it same thing, HyperDX, rebranded as ClickStack?
- mikeshi42 1y agoThis is good feedback to make things more clear :) HyperDX is part of ClickStack, so ClickStack = { HyperDX, ClickHouse, OTel }. This is the stack we recommend that will deploy in seconds and _just work_, and can scale up to PB+ and beyond as well with some additional effort (more than a few seconds unfortunately, but one day...) HyperDX v2, the version that is now stable and shipped in ClickStack, focuses more on the querying layer. It lets users have more customization around ClickHouse (virtually any schema, any deployment). Optionally, users can leverage other ways of getting data into ClickHouse like Vector, S3, etc. but still use HyperDX v2 on top. Previously in HyperDX v1 you _had_ to use OTel and our ingestion pipeline and our schemas. This is no longer true in v2. Let me know if this explanation helps