Alternatives to Grafana Tempo

Store and query distributed traces with a dedicated tracing back end. The listings below can replace it for an important use case. Each note says what changes if you switch.

The original

Replacements

Listings that take over the same core job as Grafana Tempo.

  • Jaeger

    Follow requests across services to investigate distributed-system latency.

    Jaeger collects and presents distributed traces with its own interface under Apache-2.0, instead of relying on Grafana for trace exploration and object storage.

  • Zipkin

    Collect trace timing data to troubleshoot service-to-service latency.

    Zipkin collects trace timing data and offers trace lookup under Apache-2.0, needing instrumented applications and its own storage configuration rather than object storage.

  • Apache SkyWalking

    Observe distributed applications through traces, metrics and related service information.

    Apache SkyWalking adds application-performance views and metrics alongside traces, which requires deploying its collectors and configuring supported instrumentation.

  • Pinpoint

    Trace application requests across distributed services.

    Pinpoint traces requests and visualises service relationships, but supported languages and frameworks need its own compatible agents rather than generic trace instrumentation.

  • SigNoz

    Open-source full-stack observability platform built on OpenTelemetry and ClickHouse.

    SigNoz stores traces together with logs, metrics and APM in one OpenTelemetry and ClickHouse platform, adding the overhead of running a ClickHouse-backed stack.

  • Uptrace

    Explore traces, metrics and logs collected through OpenTelemetry.

    Uptrace explores OpenTelemetry traces linked with metrics and logs in its own AGPL-3.0 interface, requiring instrumentation and a supported storage setup.

Similar software

Related functionality, not a direct replacement.