opentelemetry-specification VS jaeger

Compare opentelemetry-specification vs jaeger and see what are their differences.

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
opentelemetry-specification jaeger
100 97
3,652 19,906
0.7% 1.3%
9.3 9.8
4 days ago 4 days ago
Makefile Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of opentelemetry-specification. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-06-14.
  • The Problem with OpenTelemetry
    7 projects | | 14 Jun 2024
    Well actually. They (python SDK maintainers) argue their implementation is the correct one according to the spec. See this issue thread for example.

    There are more. This is a symptom of a how hard it is to dive into Otel due to its surface area being so big.

  • OpenTelemetry Journey #00 - Introduction to OpenTelemetry
    4 projects | | 25 Feb 2024
    It means that the OpenTelemetry project provides not only a specification to define the contract between the applications, collectors, and telemetry databases, but also a set of APIs, SDKs, and tools like instrumentation libraries (for different languages), collectors, operators, etc. OpenTelemetry is open-source and vendor-agnostic, so the project is not tied to any specific vendor or cloud provider.
  • Migrating to OpenTelemetry
    8 projects | | 16 Nov 2023
    Sure, happy to provide more specifics!

    Our main issue was the lack of a synchronous gauge. The officially supported asynchronous API of registering a callback function to report a gauge metric is very different from how we were doing things before, and would have required lots of refactoring of our code. Instead, we wrote a wrapper that exposes a synchronous-like API:

    It seems like this is a common feature request across many of the SDKs, and it's in the process of being fixed in some of them ( I'm not sure what the plans are for the golang SDK specifically.

    Another, more minor issue, is the lack of support for "constant" attributes that are applied to all metrics. We use these to identify the app, among other use cases, so we added wrappers around the various "Add", "Record", "Observe", etc. calls that automatically add these. (It's totally possible that this is supported and I missed it, in which case please let me know!).

    Overall, the SDK was generally well-written and well-documented, we just needed some extra work to make the interfaces more similar to the ones were were using before.

  • OpenTelemetry Exporters - Types and Configuration Steps
    5 projects | | 30 Oct 2023
    OpenTelemetry is an open-source collection of tools, APIs, and SDKs that aims to standardize the way we generate and collect telemetry data. It follows a specification-driven development. The OpenTelemetry specification  has design and implementation guidelines for how the instrumentation libraries should be implemented. In addition, it provides client libraries in all the major programming languages that follow the specification.
  • OpenTelemetry in 2023
    36 projects | | 28 Aug 2023
    Two problems with OpenTelemetry:

    1. It doesn't know what the hell it is. Is it a semantic standard? Is a protocol? It is a facade? What layer of abstraction does it provide? Answer: All of the above! All the things! All the layers!

    2. No one from OpenTelemetry has actually tried instrumenting a library. And if they have, they haven't the first suggestion on how instrumenters should actually use metrics, traces, and logs. Do you write to all three? To one? I asked this question two years ago, not a single response. [1]


  • Tracetest Analyzer: Identify patterns and issues with code instrumentation
    3 projects | | 7 Jul 2023
    OpenTelemetry Specification GitHub
  • OpenTelemetry vs. OpenMetrics: Which semantic convention should you use?
    2 projects | /r/PrometheusMonitoring | 2 Jun 2023
    One update to this: we proposed replacing the count suffix in OpenTelemetry with total to match Prometheus/OpenMetrics. That discussion resulted in the count suffix being removed from the OpenTelemetry semantic conventions. We'll soon update our metric from being called function.calls.count to just function.calls and the generated Prometheus queries will refer to function_calls_total. That resolves one of the main conflicts between the two specs.
  • OpenTelemetry Logs status?
    1 project | /r/OpenTelemetry | 8 Feb 2023
    This is your best bet if you want to track status updates:
  • Distributed Tracing with OpenTelemetry - Part I
    2 projects | | 7 Feb 2023
    OpenTelemetry is a standard for implementing telemetry in your applications. It provides a specification, containing the requirements that all implementations should follow as well as some implementations for major languages, including an API and a SDK to interact with it.
  • Observability - ApostropheCMS, OpenTelemetry, and New Relic
    4 projects | | 16 Nov 2022
    At this point, we are about to do the real work where we have to configure OpenTelemetry and export telemetry data to New Relic. Exporting this kind of data relies on a specific protocol; the OpenTelemetry Protocol or OTLP.


Posts with mentions or reviews of jaeger. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-07-18.
  • Instrumenting Django Applications using OpenTelemetry
    5 projects | | 18 Jul 2024
    In this articles we are going to go through instrumentating your django application using OTel. The project will demonstrate how to add logging for Prometheus and how to visualised spans using Jaeger.
  • OpenTelemetry Trace Context Propagation for gRPC Streams
    7 projects | | 19 Jun 2024
    First, you need to set up a basic infrastructure, with an OpenTelemetry (OTel) Collector to receive traces and Jaeger to store them, structuring the system like this:
  • Golang REST API boilerplate
    12 projects | | 4 Jun 2024
  • Observability with OpenTelemetry, Jaeger and Rails
    1 project | | 22 Feb 2024
    Jaeger maps the flow of requests and data as they traverse a distributed system. These requests may make calls to multiple services, which may introduce their own delays or errors.
  • Show HN: An open source performance monitoring tool
    2 projects | | 1 Feb 2024
    As engineers at past startups, we often had to debug slow queries, poor load times, inconsistent errors, etc... While tools like Jaegar [2] helped us inspect server-side performance, we had no way to tie user events to the traces we were inspecting. In other words, although we had an idea of what API route was slow, there wasn’t much visibility into the actual bottleneck.

    This is where our performance product comes in: we’re rethinking a tracing/performance tool that focuses on bridging the gap between the client and server.

    What’s unique about our approach is that we lean heavily into creating traces from the frontend. For example, if you’re using our Next.js SDK, we automatically connect browser HTTP requests with server-side code execution, all from the perspective of a user. We find this much more powerful because you can understand what part of your frontend codebase causes a given trace to occur. There’s an example here [3].

    From an instrumentation perspective, we’ve built our SDKs on-top of OTel, so you can create custom spans to expand highlight-created traces in server routes that will transparently roll up into the flame graph you see in our UI. You can also send us raw OTel traces and manually set up the client-server connection if you want. [4] Here’s an example of what a trace looks like with a database integration using our Golang GORM SDK, triggered by a frontend GraphQL query [5] [6].

    In terms of how it's built, we continue to rely heavily on ClickHouse as our time-series storage engine. Given that traces require that we also query based on an ID for specific groups of spans (more akin to an OLTP db), we’ve leveraged the power of CH materialized views to make these operations efficient (described here [7]).

    To try it out, you can spin up the project with our self hosted docs [8] or use our cloud offering at The entire stack runs in docker via a compose file, including an OpenTelemetry collector for data ingestion. You’ll need to point your SDK to export data to it by setting the relevant OTLP endpoint configuration (ie. environment variable OTEL_EXPORTER_OTLP_LOGS_ENDPOINT [9]).

    Overall, we’d really appreciate feedback on what we’re building here. We’re also all ears if anyone has opinions on what they’d like to see in a product like this!










  • Kubernetes Ingress Visibility
    2 projects | /r/kubernetes | 10 Dec 2023
    For the request following, something like jeager, because you are talking more about tracing than necessarily logging. For just monitoring, would be the starting point, then it depends. Nginx gives metrics out of the box, then you can pull in the dashboard like , or full metal with something like service mesh monitoring which would provably fulfil most of the requirements
  • Migrating to OpenTelemetry
    8 projects | | 16 Nov 2023
    Have you checked out Jaeger [1]? It is lightweight enough for a personal project, but featureful enough to really help "turn on the lightbulb" with other engineers to show them the difference between logging/monitoring and tracing.


  • The Road to GraphQL At Enterprise Scale
    6 projects | | 8 Nov 2023
    From the perspective of the realization of GraphQL infrastructure, the interesting direction is "Finding". How to find the problem? How to find the bottleneck of the system? Distributed Tracing System (DTS) will help answer this question. Distributed tracing is a method of observing requests as they propagate through distributed environments. In our scenario, we have dozens of subgraphs, gateway, and transport layer through which the request goes. We have several tools that can be used to detect the whole lifecycle of the request through the system, e.g. Jaeger, Zipkin or solutions that provided DTS as a part of the solution NewRelic.
  • OpenTelemetry Exporters - Types and Configuration Steps
    5 projects | | 30 Oct 2023
    Jaeger is an open-source, distributed tracing system that monitors and troubleshoots the flow of requests through complex, microservices-based applications, providing a comprehensive view of system interactions.
  • Fault Tolerance in Distributed Systems: Strategies and Case Studies
    4 projects | | 18 Oct 2023
    However, ensuring fault tolerance in distributed systems is not at all easy. These systems are complex, with multiple nodes or components working together. A failure in one node can cascade across the system if not addressed timely. Moreover, the inherently distributed nature of these systems can make it challenging to pinpoint the exact location and cause of fault - that is why modern systems rely heavily on distributed tracing solutions pioneered by Google Dapper and widely available now in Jaeger and OpenTracing. But still, understanding and implementing fault tolerance becomes not just about addressing the failure but predicting and mitigating potential risks before they escalate.

What are some alternatives?

When comparing opentelemetry-specification and jaeger you can also consider the following projects:

Sentry - Developer-first error tracking and performance monitoring

Serilog - Simple .NET logging with fully-structured events

skywalking - APM, Application Performance Monitoring System

zipkin - Zipkin is a distributed tracing system

prometheus - The Prometheus monitoring system and time series database.

pino - 🌲 super fast, all natural json logger

signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool

Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required

Pinpoint - APM, (Application Performance Management) tool for large-scale distributed systems.

otel-with-apache-pulsar - Example of application that produces and consumes events to/from Apache Pulsar. Traces from the transactions are captured using OpenTelemetry and sent to Elastic Observability.

fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives