Hacker News new | ask | show | jobs
by candiddevmike 1031 days ago
IMO, Jaeger is easier to setup/manage and has a better interface than Grafana/Tempo. It's easy to add Jaeger to your local dev stack so you can have tracing while developing.

FWIW I now use Tempo because I have everything else in Grafana (Prometheus, Loki), but I do miss using Jaeger.
2 comments
number101010 1031 days ago
> It's easy to add Jaeger to your local dev stack so you can have tracing while developing.

Tempo can be spun up with docker compose using a local disk for ephemeral storage/querying: https://github.com/grafana/tempo/blob/main/example/docker-co...

Maybe this meets your needs?

> Jaeger is easier to setup/manage and has a better interface than Grafana/Tempo

What do you enjoy about the Jaeger interface? Perhaps it's a gap in Tempo we can improve.

link
sofixa 1031 days ago
Jaeger can use multiple backends for storage, including Tempo, so it's not an either/or situation.

I'm fairly sure there was an official Grafana-provided Jaeger gRPC plugin for Tempo, but can't easily find it, only this one: https://github.com/flitnetics/jaeger-tempo

link