41–50 of 88 posts
There’s so many of these log aggregators I’ve completely lost track. I used Datadog extensively and found it overpriced and a very confusing UI.
It would have even much better if the link was pointing to https://github.com/hyperdxio/hyperdx the actual source code. Because right now without the message on HN here, I wouldn't know what "open source observability stack" meant when the webpage does not explain what HyperDX is, nor does it provide a link to it or its code. I was expecting the whole thing "Open Source Datadog" to be ClickStack Repo inside Clickhous…
We started building signoz as an OS alternative of Datadog/New Relic four years back and opentelemetry-native from day 1. We have shipped some good features on top of Opentelemetry and because of OTel's semantic conventions & our query builder, you can correlate any telemetry across signals.
Earlier quoted context omitted.
First 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…
Still 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?
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
Do i need to sign-in when using the docker container?
Otherwise yes you can authenticate against the other versions with a email/password (really the email doesn't do anything in the open source distribution, just a user identifier but we keep there to be consistent)
I liked Otel for traces and maybe logging -- but I think the Otel metrics is over-engineered. Does ClickStack have a way to ingest statsd data, preferably with Datadog extensions (which adds tagging)? Does ClickStack offer correlations across traces, logging, and metrics via unified service tagging? Does the UI offer the ability to link to related traces, logging, and metrics? Why does the Elixir sdk use the hyperdx…
Great questions! OTel Metrics: I get it, it's specified as almost a superset of everyone's favorite metric standards with config for push/pull, monotonic vs delta, exponential/"native" histograms, etc. I have my preferences as well which would be a subset of the standard but I get why a unifying standard needed to be flexible. Statsd: The great thing about the OTel collector is that it allows ingesting a variety of d…
I think this is enough features for me to seriously take a look at it as a Datadog alternative.
I spent some time writing an integration for HyperDX after seeing this post and hope you can help me roll it out! Would love to add a new "integrations" section to my page that links to the docs on how to use HyperDX with LogLayer.
The dashboards and their creation are intuitive. Creating alerts and things from airflow logs is easy using their DSL. Connecting and sending notifications to things like slack just works tm.
So this is how we justify the datadog costs because of all the engineering time (engineers are still expensive, ai hasn’t replaced us yet) it saves and how quickly we can move from raw logs and metrics to useful insights.
I am absolutely amazed at the amount of garbage being "logged", enough that it is not just a huge business, but also one of the primary task for some devops guys. It's like a goal in itself, you have a look at the output and it is absolutely scary, HUGE messages being "logged" for purpose unknown. I've seen single traces over 100KB of absolute pure randomness encoded as base64... Because! Oh and also, we have to pay…
Earlier quoted context omitted.
In theory you should be able to try using FerretDB for example. We have this on the medium term roadmap to investigate proper support for a compatibilty layer such as ferret or more likely just using ClickHouse itself as the operational data store.
FerretDB maintainer here - we'll be looking at this