Dash0's company blog on OpenTelemetry-based observability, covering tracing, logging, Kubernetes, and monitoring tools.
Commenters say its articles' setups work with most modern observability tools, and one criticizes its docs for vague Kubernetes version requirements. It also posts job ads.
Dash0 | Senior Product Engineer - Backend | Full-time | REMOTE (Europe) | https://www.dash0.com/ Imagine a world where observability is... well, easy. That's what we're building at Dash0. We're not just another observability company – we're a team of passionate experts who are obsessed with making observability accessible and delightful for every developer.
We are OpenTelemetry native, ensuring seamless interoperability within modern observability ecosystems, and our “welcome present” to the OpenTelemetry community, OTelBin, a free tool for editing, visualization and validation of OpenTelemetry collector configurations, is being extremely well received by the community.
We're looking for Senior Product Engineers to join our awesome team and help us build the best observability tool out there. You'll be working with cutting-edge tech and collaborating closely with product and design to create a truly user-friendly experience.
If our mission resonates with you, check out the full job description and apply here: https://careers.dash0.com/senior-product-engineer-backend/en
We're also hiring for other positions (GCP, Kubernetes Operator, Frontend), make sure to check out our careers page to see all the opportunities: https://careers.dash0.com/?lang=en
To be fair, the setup of the article works with most modern observability solutions, in same cases just by replacing the endpoint and authentication token. Turning telemetry processing into a sort of utility is one of the great things that OpenTelemetry did. Now, among vendors, we compete on delivering insights on the telemetry, as opposed to just collecting it. If you are interested, I wrote about it a while back [1].
About excessive telemetry, that depends on what you want to achieve. Using facilities in the OpenTelemetry Collector like [2], you can easily drop all telemetry you have no use for. At the cost of tooting my own horn, we actually provide super easy ways of doing the same dropping at no charge whatsoever to the end user in Dash0 [3].
[1] https://thenewstack.io/is-otel-the-last-observability-agent-youll-ever-install/
[2] https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/filterprocessor
[3] https://www.dash0.com/changelog/spam-filters
In kubernetes having "version one, minor whatever" isn'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 https://www.dash0.com/documentation/dash0/dash0-kubernetes-operator#prerequisites
Chasing https://github.com/dash0hq/dash0-operator/blob/0.35.3/go.mod#L24 into https://github.com/kubernetes/client-go/tree/v0.31.3#compatibility-matrix doesn't even mention any of the 1.30+ series but based solely upon the .31 part it sure does seem like it's a bleeding edge client-go