Get the latest tech news

I got OpenTelemetry to work. But why was it so complicated?


A number of our customers have recently been asking whether we support OpenTelemetry, the observability framework and toolkit. When the first member of the team who’s client-facing asked me – the go-to guy...

I don’t really understand why there are four, but I think what’s happened is convergent evolution: different sets of people – unaware of one another – came to a shared conclusion regarding how to solve a specific problem. Metrics: Spring and Akka expose different Prometheus endpoints so won’t step on each other’s toes Logs: We use SLF4J and Logback which is common to both frameworks Traces: Both used OpenTracing , because Lightbend Telemetry uses a custom Tracer implementation which makes the shim and Jaeger freak out, and, instead of any of these things doing their job and propagating a trivial string-string map, spams the log with:

Get the Android app

Or read this on Hacker News

Read more on:

Photo of opentelemetry

opentelemetry

Related news:

News photo

OpenTelemetry and vendor neutrality: how to build an observability strategy

News photo

The problem with OpenTelemetry

News photo

Show HN: OpenLIT – Open-Source LLM Observability with OpenTelemetry