TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: Dash0 – Dev-Friendly OpenTelemetry Observability with Open Standards

14 点作者 de1075495 个月前
Hey HN!<p>After building an observability software (Instana) and selling it to IBM, I wanted to approach observability differently this time—simpler, more open, and built with developers like me in mind. That’s why I started Dash0.<p>Dash0 is natively built on OpenTelemetry, so logs, metrics, and traces are handled without extra hoops. You can send data via OTLP directly, through an OpenTelemetry Collector, or use our open-source Kubernetes operator to get started quickly.<p>I didn’t want a tool that forces people into proprietary systems, so Dash0 supports PromQL for querying and alerting and Perses for dashboards. If you’ve already got queries or alerts from Prometheus, you can reuse them with Dash0 without any friction. We went the extra mile, exposing logging and tracing data to PromQL, too, in a way that feels native.<p>One thing I always found frustrating about other tools was the need for more context. Dash0 leverages OpenTelemetry’s semantic conventions to tie all signals together. It correlates logs, metrics, and traces around the resource concept, which makes it easier to filter, search, and navigate between dependencies.<p>On the user experience side, I focused on making it developer- and SRE-friendly. Everything has full keyboard support, quick filtering with previews and guidance, and APIs that help you get answers fast, not just clicks and dashboards. I wanted something that feels snappy and productive, not clunky and unwieldy.<p>Dash0 is still in its early days, but it’s a tool I would have wanted myself—an open platform that rejects lock-in and works with the tools and open standards we already use in the cloud-native community.<p>I’d love to hear your feedback, suggestions, or thoughts on observability in general.

3 条评论

mdaniel5 个月前
In kubernetes having &quot;version one, minor whatever&quot; isn&#x27;t meaningful because I can assure you with absolute confidence that 1.2 != 1.30 so it would be helpful to include the actual, no kidding, minimum version that you support <a href="https:&#x2F;&#x2F;www.dash0.com&#x2F;documentation&#x2F;dash0&#x2F;dash0-kubernetes-operator#prerequisites" rel="nofollow">https:&#x2F;&#x2F;www.dash0.com&#x2F;documentation&#x2F;dash0&#x2F;dash0-kubernetes-o...</a><p>Chasing <a href="https:&#x2F;&#x2F;github.com&#x2F;dash0hq&#x2F;dash0-operator&#x2F;blob&#x2F;0.35.3&#x2F;go.mod#L24">https:&#x2F;&#x2F;github.com&#x2F;dash0hq&#x2F;dash0-operator&#x2F;blob&#x2F;0.35.3&#x2F;go.mod...</a> into <a href="https:&#x2F;&#x2F;github.com&#x2F;kubernetes&#x2F;client-go&#x2F;tree&#x2F;v0.31.3#compatibility-matrix">https:&#x2F;&#x2F;github.com&#x2F;kubernetes&#x2F;client-go&#x2F;tree&#x2F;v0.31.3#compati...</a> doesn&#x27;t even mention any of the 1.30+ series but based solely upon the .31 part it sure does seem like it&#x27;s a bleeding edge client-go
评论 #42389277 未加载
评论 #42380993 未加载
o11ydev5 个月前
What’s the difference between this and other o11y tools that use Otel? Seems like just a new UI + storage layer for otel. Every o11y company is now allowing for telemetry to be sent via otel, so how is this any more “open” or “lock-in” free than any other vendor?
评论 #42379015 未加载
shahahmed5 个月前
i like the philosophy! do ya&#x27;ll provide a specific collector&#x2F;agent or do users send directly from the community otel collector?
评论 #42380224 未加载
评论 #42380207 未加载