open-telemetry/opentelemetry-erlang
This system is an OpenTelemetry implementation for Erlang and Elixir, providing a complete distributed tracing and metrics instrumentation framework. It exposes APIs for creating and managing spans, logs, and various metric instruments, while supporting context propagation and baggage. The SDK handles span processing, sampling, and resource detection, and offers exporters for the OpenTelemetry Protocol (OTLP) and Zipkin.
76.7
Strong · 1 August 2026
67k
lines of production code
Erlang
with Elixir
1
bus factor · 82 authors in all
3
measurements over time
How it got here
2019–2020 · OpenTelemetry API and SDK implementation
This period focused on establishing the foundational components for distributed tracing, introducing the standalone OpenTelemetry API and updating the SDK to version 1.7.0 with a new centralized configuration system. The work included implementing core tracing features such as context propagation, baggage management, and batch span processing, alongside the initial release of the OTLP exporter for Erlang and Elixir.
19 changes
2021–2022 · experimental metrics and semantic conventions
This period focused on introducing experimental support for metrics, including a new API for counters, histograms, and gauges, alongside the creation of a dedicated experimental application. It also involved establishing semantic conventions for attributes and deprecating older macro-based definitions, while adding initial exporters for Zipkin.
18 changes
2023–2024 · OpenTelemetry semantic conventions v1.40.0 update
This period focused on upgrading the OpenTelemetry semantic conventions to version 1.40.0, introducing new attributes and metrics for domains such as Azure, CI/CD, and GenAI. The work involved generating and testing Elixir and Erlang code templates, updating schema URL mappings, and implementing stability opt-in configurations.
11 changes
Survey your own repository
open-telemetry/opentelemetry-erlang was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 4cc1e9ba6a — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.