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

Re:I got OpenTelemetry to work. But why was it so complicated? by PeterCorless on Friday January 10, 2025 @06:07PM (#42661405)

For tracing FOSS: Grafana Tempo.

https://grafana.com/oss/tempo/

[ Parent | on HN ]

Re:I got OpenTelemetry to work. But why was it so complicated? by flurie on Friday January 10, 2025 @06:25PM (#42661561)

Tempo's a backend/sink for traces, but if you click through to the Tempo docs and find out how to generate tracing data[1], you learn that you have two options: OpenTelemetry, which they recommend, and Zipkin, which they do not recommend.

[1] https://grafana.com/docs/tempo/latest/getting-started/instru...

[ Parent | on HN ]

Re:I got OpenTelemetry to work. But why was it so complicated? by paulddraper on Saturday January 11, 2025 @05:11PM (#42669338)

"I don't want solutions, I want to be mad."

[ Parent | on HN ]

Re:I got OpenTelemetry to work. But why was it so complicated? by thephyber on Friday January 10, 2025 @09:03PM (#42662623)

Tempo is a traces server. Prometheus is a metrics server.

Grafana, the same company that develops and sells Tempo created a horizontally scalable version of Prometheus called Mimir.

OpenTelemetry is an ecosystem, not just 1 app. It’s protocols, libraries, specs, a Collector (which acts as a clearinghouse for metrics+traces+logs data). It’s bigger than just Tempo. The intention of Patel seems to be to decouple the protocol from the app by having adapters for all of the pieces.

[ Parent | on HN ]

Re:I got OpenTelemetry to work. But why was it so complicated? by Too on Saturday January 11, 2025 @02:48AM (#42664134)

Prometheus is not only a metrics server, it's also become the de-facto metrics exposition format.

[ Parent | on HN ]