Specifications for OpenTelemetry (by open-telemetry)

Opentelemetry-specification Alternatives

Similar projects and alternatives to opentelemetry-specification

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better opentelemetry-specification alternative or higher similarity.

opentelemetry-specification reviews and mentions

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-02-25.
  • 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.
  • 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.
  • OpenTelemetry Logs - A Complete Introduction & Implementation
    3 projects | | 20 Oct 2022
    OpenTelemetry provides instrumentation libraries for your application. The development of these libraries is guided by the OpenTelemetry specification. The OpenTelemetry specification describes the cross-language requirements and design expectations for all OpenTelemetry implementations in various programming languages.
  • An Open Source Observability Platform | SigNoz
    3 projects | | 13 Oct 2022
    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 which follow the specification.
  • A note from our sponsor - InfluxDB | 16 Apr 2024
    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. Learn more →


Basic opentelemetry-specification repo stats
5 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives