51–60 of 88 posts
(The UI looks similar too, although I guess a lot of observability tools seem to adopt that kind of UI).
Datadog is expensive this is true. But I have never felt it be slow. Speed is not its killer feature. It’s everything you can do with it once you have logs and or metrics flowing into it. 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 co…
Beyond raw performance and cost effectiveness, which is quite important at scale, we work a lot on making sure the application layer itself is intuitive to use. You can always play around with what ours looks like at play.hyperdx.io :)
While I do like the stack we have, it is a lot of components to run and configure. Don’t think we have ever had any issues once it was up and running.
Does anyone have any thoughts about how this compares? We don’t have a huge amount of days, 1 month of metrics is about 200GB and logs isn’t a whole lot more, less than a TB I think for 2 weeks.
I'm looking for a new logging solution to replace Kibana. I have very good experience with ClickHouse, and HyperDX looks like a decent UI for it. I'm primarily interested in logs, though, and the existing log shipping pipeline is around Vector on Kubernetes. Admittedly Vector has an OTel sink in beta, but I'm curious if that's the best/fastest way to ship logs, especially given that the original data comes out of app…
Earlier quoted context omitted.
I agree - rotel seems like a really good fit for a lightweight lambda integration for OTel, it of course should work already since we stand up an OTel ingest endpoint so it should be seamless to send data over! (Kind of the beauty of OTel of course) I've also been in touch with Mike & Ray for a bit, who've told me they've added ClickHouse support recently which makes the story even better :)
Hi all — one of the authors of Rotel here. Thanks for the kind words, Bilal and Michael. We're excited to test our Clickhouse integration with Clickstack, as we believe OTel and Clickhouse make for a powerful observability stack. Our open-source Rust OpenTelemetry collector is designed for high-performance, resource-constrained environments. We'd love for you to check it out!
This is really cool considering how expensive DataDog can get. I'm the author of LogLayer ( https://loglayer.dev ), which is a structured logger for TypeScript that allows you to use multiple loggers together. I've written transports that allows shipping to other loggers like pino and cloud providers such as DataDog. I spent some time writing an integration for HyperDX after seeing this post and hope you can help me…
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.
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?
This 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 th…
Earlier quoted context omitted.
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?
This 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 th…
I'm just asking because you mention OTel and "other ways" in your post, and you must have a good overview over the options and where the market is headed.
I found the UX very difficult to read. The monospace font, the unusually small text, the bold white and bright green text on a dark background… I found it a little more readable by changing the font to system-ui, but not by much. Please consider a more traditional style instead of leaning into the 80s terminal gimmick. This factor alone makes me want to not use it. It needs to be easy to read, not a pain to read.