open-telemetry/opentelemetry-erlang-contrib
78.7
Strong · 15 November 2026
12.8k
lines of production code
Elixir
with Erlang
5
measurements over time
What this system is
Features
Add AWS X-Ray compatible trace ID generator
Users can now integrate with AWS X-Ray by using the new \opentelemetry\_aws\_xray\ package, which provides an \otel\_aws\_xray\_id\_generator\ that produces 128-bit trace IDs compatible with the AWS X-Ray format (timestamp + random bits). This utility depends on \opentelemetry\_api\ version 1.2 and is licensed under Apache 2.0.
_utilities/opentelemetry\_aws\xray · high confidence
Add Dataloader instrumentation library
This change introduces the \opentelemetry\_dataloader\ instrumentation library, providing configuration files for the application and test environments, along with a database migration to set up the necessary test tables (specifically a \posts\ table) for validating the instrumentation.
_instrumentation/opentelemetry\_dataloader/config, instrumentation/opentelemetry\dataloader/priv · high confidence
Add OpenTelemetry Process Propagator v0.3.0
Introduces the \opentelemetry\_process\_propagator\ library, enabling context propagation across process boundaries within the same node. The implementation provides functions to fetch the current context and inspect parent contexts by traversing process ancestors. It includes optimized lookups for Erlang/OTP 27+ via direct dictionary key access, while maintaining compatibility with earlier versions by fetching the full process dictionary and searching for the context key.
_propagators/opentelemetry\_process\propagator/src · high confidence
Add OpenTelemetry SQL Commenter library for PostgreSQL trace context injection
The \opentelemetry\_sqlcommenter\ package (v0.2.0) is now available as an Elixir library that automatically injects OpenTelemetry trace context into PostgreSQL SQL queries as comments. By delegating the \prepare\_query\ function in your Ecto repository to \OpentelemetrySqlcommenter\, database logs will include W3C-compliant \traceparent\ identifiers, linking SQL operations to distributed traces. The library defaults to disabling prepared statements (\prepare: :unnamed\) to ensure query uniqueness for logging, though it preserves any explicitly provided \prepare\ options.
_instrumentation/opentelemetry\sqlcommenter · high confidence
Add OpenTelemetry context propagation to Task.Supervisor
The \opentelemetry\_process\_propagator\ library now provides \OpentelemetryProcessPropagator.Task.Supervisor\ and \OpentelemetryProcessPropagator.Task.Wrapper\ modules to automatically propagate OpenTelemetry context across process boundaries. These modules offer convenience functions like \async\, \async\_with\_span\, and \async\_with\_linked\_span\ that replicate \Task.Supervisor\ behavior while ensuring the current trace context is attached in the spawned task, or creating new child/linked spans as needed. This allows users to maintain distributed tracing continuity without manually handling context attachment in every asynchronous task.
_propagators/opentelemetry\_process\propagator/lib/task · high confidence
Add OpenTelemetry instrumentation for Nebulex caches
The new \opentelemetry\_nebulex\ library automatically creates OpenTelemetry spans for Nebulex cache commands (such as \get\, \put\, and \fetch\) by attaching to Telemetry events. It supports both Nebulex v2 and v3, providing detailed span attributes including the cache name, database system, operation name, query text, and cache hit/miss status, enabling users to trace and monitor their caching layer performance.
_instrumentation/opentelemetry\nebulex · high confidence
Add Phoenix + Ecto OpenTelemetry example application
Introduces a new example project in \examples/basic\_phoenix\_ecto\ that demonstrates how to integrate OpenTelemetry tracing with a Phoenix web application and Ecto database layer. The example includes a full Phoenix application structure with Ecto schemas for users and posts, configured to export traces via the OpenTelemetry Collector to local Zipkin and Jaeger instances, with optional support for Honeycomb and Lightstep. It provides a \docker-compose.yaml\ to run the application alongside PostgreSQL, the Collector, Zipkin, and Jaeger, along with a Dockerfile for containerized releases and configuration files for development, testing, and production environments.
_examples/basic\_phoenix\ecto · high confidence
Add grpcbox OpenTelemetry interceptor for distributed tracing
This change introduces the \opentelemetry\_grpcbox\ library, an interceptor for the grpcbox framework that automatically creates OpenTelemetry spans for gRPC client and server requests. It propagates trace context via gRPC metadata, allowing distributed traces to span across gRPC boundaries. The package includes server and client interceptor implementations, configuration examples, and a comprehensive test suite using the RouteGuide proto to verify trace context propagation.
_instrumentation/opentelemetry\grpcbox · high confidence
Add roll dice example using Elli and OpenTelemetry
This change introduces a new example application demonstrating an Erlang-based web server using the Elli library. The frontend, located in the JavaScript and static HTML files, utilizes HTMX for dynamic interactions and integrates OpenTelemetry for distributed tracing, configuring a WebTracerProvider with console and OTLP exporters to monitor the 'roll-dice-ui' service.
_examples/roll\_dice\_elli/js, examples/roll\_dice\elli/priv · high confidence
Initial OpenTelemetry instrumentation for Oban job queues
Adds the \OpentelemetryOban\ library to automatically create OpenTelemetry spans for Oban background job events, including job start, stop, and exceptions. The module provides a \setup/1\ function to initialize telemetry handlers, supporting configurable options for job and plugin tracing via \NimbleOptions\. It also wraps Oban's \insert\ and \insert\_all\ functions to record producer spans with messaging semantic conventions, allowing users to trace job submission alongside execution.
_instrumentation/opentelemetry\oban/lib · high confidence
Initial OpenTelemetry instrumentation for Oban jobs and plugins
Adds OpenTelemetry tracing support for Oban background job processing and plugin lifecycle events. The new \JobHandler\ module instruments job start, stop, and exception events, attaching spans with semantic conventions for messaging systems (identifying Oban as the system) and custom attributes such as job ID, worker, queue, priority, attempt counts, and timing metrics. It supports configurable context propagation via \span\_relationship\ options (\:child\, \:link\, or \:none\). The \PluginHandler\ module instruments Oban plugins (including Cron, Gossip, Lifeline, Pruner, and Pro variants), recording plugin-specific metrics like job counts, discarded/rescued jobs, and scaling events, while properly handling plugin failures and exceptions.
_instrumentation/opentelemetry\_oban/lib/opentelemetry\oban · high confidence
Initial configuration for the Erlang Elli roll-dice example
This change introduces the initial configuration files for the new Erlang roll-dice example application. The sys.config sets up the application environment, configures OpenTelemetry to use the OTLP exporter for traces and metrics (with a batch span processor and 1-second metric export interval), excludes static paths from tracing, and sets the logger level to debug. The vm.args file defines the node name and cookie for distributed Erlang communication.
_examples/roll\_dice\elli/config · high confidence
Initial release of OpenTelemetry Dataloader instrumentation
This entry introduces the \opentelemetry\_dataloader\ library, a new telemetry handler for Elixir applications that automatically creates OpenTelemetry spans from Dataloader events. By calling \OpentelemetryDataloader.setup()\ in the application behavior before the top-level supervisor starts, users can instrument Dataloader run and batch operations. The library attaches to \\[:dataloader, :source, :run, :start/:stop\]\ and \\[:dataloader, :source, :batch, :run, :start/:stop\]\ events, creating client spans named \dataloader.run\ and \dataloader.batch\. It preserves the current OpenTelemetry context or falls back to the caller's context (up to 4 levels deep) to ensure proper trace propagation. For batch operations, it extracts attributes such as \dataloader.batch\_key\ from the metadata, supporting both Ecto sources (MapSet) and KV sources (atom or binary keys).
_instrumentation/opentelemetry\_bandit, instrumentation/opentelemetry\dataloader · high confidence
Initial release of OpenTelemetry Dataloader instrumentation
This entry introduces the \opentelemetry\_dataloader\ library, which automatically instruments the Dataloader library by creating OpenTelemetry spans from Dataloader telemetry events. Users can enable this by calling \OpentelemetryDataloader.setup/0\ in their application behavior before the top-level supervisor starts. The library attaches to \:dataloader.source.run\ and \:dataloader.source.batch\ events, creating client spans for individual runs and batches. It specifically handles context propagation by attaching the parent context from the current process or its callers, and enriches batch spans with attributes identifying the batch key for both Ecto sources (MapSet) and KV sources (atom or binary keys).
_instrumentation/opentelemetry\redix · high confidence
Initial release of OpenTelemetry Process Propagator v0.3.0
This change introduces the OpenTelemetry Process Propagator library, which provides functions for cross-process OpenTelemetry context propagation. The v0.3.0 release includes a fix allowing the propagator to look up the parent context when the parent is a named process, and adds support for Elixir 1.15 and OTP 26. The package depends on opentelemetry\_api and opentelemetry\_semantic\_conventions.
_propagators/opentelemetry\_process\propagator · high confidence
Initial release of OpenTelemetry Telemetry bridge
This change introduces the \opentelemetry\_telemetry\ application (version 1.1.2), which bridges Erlang/OTP Telemetry events to OpenTelemetry spans. The module \otel\_telemetry\ implements handlers for start, stop, and exception events, managing span context via a tracer stack to ensure correct parent-child relationships. It depends on \opentelemetry\, \opentelemetry\_api\, and \telemetry\.
_utilities/opentelemetry\telemetry/src · high confidence
Initial release of opentelemetry\_elli middleware
Adds the opentelemetry\_elli library, providing Elli middleware for OpenTelemetry HTTP instrumentation. The middleware automatically creates server spans, extracts trace context from W3C and B3 headers, and records HTTP attributes (such as method, path, status code, and server address) according to Semantic Conventions v1.27+. It supports excluding specific paths from tracing via application config or the OTEL\_ELLI\_EXCLUDED\_PATHS environment variable and includes a Common Test suite to verify span creation and context propagation.
_instrumentation/opentelemetry\elli · high confidence
Initial release of opentelemetry\_telemetry utility
This change introduces the \opentelemetry\_telemetry\ library, which allows BEAM applications to create OpenTelemetry spans from existing \telemetry\ events. The package depends on \opentelemetry\_api\ (v1.3) and \telemetry\ (v1.1), and includes a test suite that verifies span creation, nesting, and exception handling via telemetry event handlers. Also in this area: 1 commit adding/updating tests in utilities.
_utilities/opentelemetry\_telemetry, utilities/opentelemetry\telemetry/test · high confidence
Introduce OpenTelemetry instrumentation for gRPC clients and servers
Adds the \opentelemetry\_grpc\ library, providing automatic distributed tracing for gRPC applications in Elixir. The package includes client instrumentation that creates spans for outgoing RPC calls and a context propagator interceptor to inject trace headers, as well as server instrumentation that creates spans for incoming requests with configurable span relationships (child, link, or none). It follows OpenTelemetry semantic conventions for RPC attributes and error status codes.
_instrumentation/opentelemetry\grpc · high confidence
Introduce OpenTelemetry middleware for Tesla HTTP client
Adds the \opentelemetry\_tesla\ library, providing a Tesla middleware that creates OpenTelemetry spans and injects distributed tracing headers into outgoing HTTP requests. The middleware implements Client HTTP Span semantic conventions, allowing users to configure opt-in experimental attributes (such as URL templates and body sizes), define static span names, and control which HTTP status codes are marked as errors. It also supports capturing specific request and response headers as span attributes and includes documentation on recommended middleware ordering to ensure accurate trace data.
_instrumentation/opentelemetry\tesla · high confidence
Introduce OpenTelemetry process context propagation helpers
Adds the \OpentelemetryProcessPropagator\ library, which provides utilities to maintain trace context across Erlang/Elixir process boundaries. The \OpentelemetryProcessPropagator\ module exposes functions like \fetch\_ctx/1\ and \fetch\_parent\_ctx/1\ to retrieve OpenTelemetry context from parent or ancestor processes, addressing the lack of transparent context passing in the runtime. Additionally, the \OpentelemetryProcessPropagator.Task\ module offers extended \Task\ functions (e.g., \async\_with\_span\, \async\_stream\_with\_linked\_span\) that automatically attach context and manage span lifecycle for concurrent tasks, reducing boilerplate and preventing orphan spans.
_propagators/opentelemetry\_process\propagator/lib · high confidence
Introduce OpentelemetryReq plugin for Req HTTP client instrumentation
Adds a new \opentelemetry\_req\ library that integrates OpenTelemetry tracing with the Req HTTP client. The plugin wraps Req requests in spans, supporting configurable opt-in semantic convention attributes (such as URL template and body size), explicit trace header propagation, and custom span name overrides. It also enforces the OpenTelemetry HTTP semantic conventions for span naming and attributes, ensuring compatibility with modern observability standards.
_instrumentation/opentelemetry\req · high confidence
Introduce OpentelemetryXandra for tracing Xandra queries
The new OpentelemetryXandra library allows users to automatically generate OpenTelemetry spans for Xandra database queries. By calling \OpentelemetryXandra.attach/1\ (formerly \setup/1\) during application startup, the library hooks into Telemetry events to record span details such as the database operation, server address, and network port, following OpenTelemetry semantic conventions for Cassandra. It supports custom query parsing via the \:operation\_parser\ option and includes a test suite with a Docker Compose setup for local validation.
_instrumentation/opentelemetry\xandra · high confidence
Introduce opentelemetry\_broadway instrumentation for Broadway pipelines
This change adds the \opentelemetry\_broadway\ library, providing OpenTelemetry tracing for Broadway message processing and batch handling. Users can enable basic instrumentation via \OpentelemetryBroadway.setup/1\ or configure distributed tracing context propagation using the \span\_relationship\ option (supporting \:link\, \:child\, or \:none\). The instrumentation attaches telemetry handlers to capture message and batch lifecycle events, emitting spans with standard messaging attributes as well as Broadway-specific metrics like successful and failed batch counts.
_instrumentation/opentelemetry\broadway · high confidence
New OpenTelemetry instrumentation for Commanded
This release adds the \opentelemetry\_commanded\ package, providing automatic OpenTelemetry tracing for Commanded-based applications. It instruments application dispatch, aggregate execution, event handler processing, process manager handling, and event store operations (such as \append\_to\_stream\ and \stream\_forward\) by attaching to Commanded's telemetry events. The package includes a middleware (\OpentelemetryCommanded.Middleware\) for propagating trace context across process boundaries and a \setup/0\ function to initialize all telemetry handlers. Users can install the package via Hex and configure it by calling \OpentelemetryCommanded.setup/0\ and adding the middleware to their Commanded routers.
_instrumentation/opentelemetry\commanded · high confidence
New OpentelemetryTelemetry module for bridging Telemetry and OpenTelemetry
A new \OpentelemetryTelemetry\ module has been added to provide helper functions (\start\_telemetry\_span\, \set\_current\_telemetry\_span\, \end\_telemetry\_span\) that allow library authors to correctly correlate telemetry events with OpenTelemetry spans. This addresses the challenge of managing span contexts across separate telemetry handlers by automatically handling parent-child relationships and context restoration, enabling seamless integration between the \telemetry\ and \opentelemetry\ libraries.
_utilities/opentelemetry\telemetry/lib · high confidence
OpentelemetryAbsinthe instrumentation library added to instrumentation directory
The \opentelemetry\_absinthe\ library (version 2.4.0) has been moved into the \instrumentation\ directory and initialized with standard project structure files including \.credo.exs\, \.formatter.exs\, and a \CHANGELOG.md\. This library provides OpenTelemetry instrumentation for Absinthe GraphQL, automatically tracing operations and subscriptions. Key features include configurable tracing of request details (query, variables, selections) and response details (result, errors), with a new \error\_status\ option to control when GraphQL errors mark a span as failed (defaulting to marking all errors as failures, but allowing \:none\ or custom functions to suppress this). It also includes helpers like \batch\_keep\_span\ to preserve OpenTelemetry context during Absinthe batch operations, and supports attaching custom metadata to telemetry events via \OpentelemetryAbsinthe.TelemetryMetadata\.
_instrumentation/opentelemetry\absinthe · high confidence
OpentelemetryFinch instrumentation for Finch HTTP client
Adds the OpentelemetryFinch package, which uses telemetry handlers to create OpenTelemetry spans from Finch HTTP client events. The instrumentation follows the Client HTTP Span v1.39 semantic conventions, allowing users to configure opt-in attributes (such as URL templates and header attributes) and custom span names via Finch request private maps. This enables distributed tracing for HTTP requests made through Finch.
_instrumentation/opentelemetry\finch · high confidence
Behavioural changes
19 commits (1 fix) modifying examples/roll\_dice
A change to existing behaviour in examples/roll\_dice — 19 commits (1 fix), 26 files: “Remove batch processor references from OpenTelemetry Collector config (\#552)”; “chore(deps): update otel/opentelemetry-collector-contrib docker tag to v0.165.0 (\#881)”; “chore(deps): update jaegertracing/jaeger docker tag to v2.21.0 (\#818)”; and 16 more (refs \#552, \#881, \#818, \#819, \#774, …).
_examples/roll\dice · medium confidence · unverified
20 commits (1 fix) modifying examples/roll\_dice\_elli
A change to existing behaviour in examples/roll\_dice\_elli — 20 commits (1 fix), 12 files: “Remove batch processor references from OpenTelemetry Collector config (\#552)”; “chore(deps): update otel/opentelemetry-collector-contrib docker tag to v0.165.0 (\#881)”; “chore(deps): update jaegertracing/jaeger docker tag to v2.21.0 (\#818)”; and 17 more (refs \#552, \#881, \#818, \#819, \#774, …).
_examples/roll\_dice\elli · medium confidence · unverified
29 commits (0 fixes) modifying examples/basic\_elixir
A change to existing behaviour in examples/basic\_elixir — 29 commits, 13 files: “Remove batch processor references from OpenTelemetry Collector config (\#552)”; “chore(deps): update patch updates (\#816)”; “chore(deps): update patch updates (\#797)”; and 26 more (refs \#552, \#816, \#797, \#881, \#818, …).
_examples/basic\elixir · medium confidence · unverified
Configuration migration to Application env and deprecation of setup/1
The \OpentelemetryHTTPoison.setup/1\ function is now deprecated; configuration should be read from the \Application\ environment (\config :opentelemetry\_httpoison\) instead. This change includes validation of configuration options (such as \:ot\_attributes\ and \:infer\_route\) at setup time, ensuring that invalid values raise errors immediately rather than upon retrieval. Additionally, the instrumentation now correctly handles atom header keys by converting them to strings for trace propagation, and fixes issues where request options like \:ot\_resource\_route\ and \:ot\_attributes\ could not be passed together or where invalid \:ot\_attributes\ were incorrectly mapped to \nil\.
_instrumentation/opentelemetry\httpoison · high confidence
Default OpenTelemetry configuration for Phoenix instrumentation
The Phoenix instrumentation now includes a default configuration file that loads environment-specific settings, and a test configuration that sets the OpenTelemetry processor to the simple processor for testing environments.
_instrumentation/opentelemetry\phoenix/config · high confidence
Fix multi-endpoint tracing and add LiveView span naming options
The \setup/1\ function now correctly instruments every Phoenix endpoint, fixing a bug where applications with multiple endpoints lost spans for all but the first one. Additionally, users can now opt into route-based span names for LiveView events (e.g., \live\_view.mount /resources/:id\) via the new \liveview\_span\_names\ option, and \handle\_event\ spans now include the \http.route\ attribute for better trace context.
_instrumentation/opentelemetry\phoenix · high confidence
Fixes to Oban plugin telemetry attributes and error reporting
This release corrects several issues in the OpenTelemetry instrumentation for Oban plugins. It restores the reporting of plugin count attributes (such as \oban.plugins.\*\_count\) which were silently dropped on Oban 2.24+ due to module name changes, and fixes a crash that occurred when the Cron plugin's stop event lacked job metadata. The instrumentation now accurately reports discarded and rescued job counts for the Lifeline plugin, properly records exception messages on plugin spans, and correctly marks plugin spans as errored when a plugin run fails. Additionally, plugin module names are now emitted in their short form (e.g., \Oban.Plugins.Cron\) without the \Elixir.\ prefix to align with configuration expectations.
_instrumentation/opentelemetry\oban · high confidence
OpenTelemetry Cowboy instrumentation v1.0.0 with Semantic Conventions v1.27.0
The \opentelemetry\_cowboy\ package has been updated to version 1.0.0, introducing breaking changes to align with OpenTelemetry Semantic Conventions v1.27.0. This release updates dependencies such as \opentelemetry\_api\ to 1.4 and \opentelemetry\_semantic\_conventions\ to 1.27, and adds support for opt-in attributes (like request body size) and public endpoint configuration to handle trace continuation versus linking. Users must review the HTTP Stability Migration Guide for details on the attribute and behavior changes.
_instrumentation/opentelemetry\cowboy · high confidence
OpentelemetryEcto 2.0.0-beta.1: Semantic Conventions v1.27 and Multi-Adapter Support
The opentelemetry\ecto instrumentation has been updated to version 2.0.0-beta.1, introducing support for OpenTelemetry Semantic Conventions v1.27 and expanding database compatibility to include MySQL, MSSQL, and SQLite in addition to existing adapters. This release brings several breaking changes: time measurement attributes are now namespaced under \ecto.\\ (e.g., \ecto.query\_time.duration\), span names now conform to the SemConv 1.27 specification, and various API adjustments have been made. Users can now configure per-query options, opt out of specific recommended attributes, and customize telemetry metadata preprocessing. The setup process now derives connection settings from \init\ events to ensure accurate host information reporting.
_instrumentation/opentelemetry\ecto · high confidence
otel\_http library renamed and updated to v0.2.0 with new header extraction utilities
The \opentelemetry\_instrumentation\_http\ package has been renamed to \otel\_http\ (v0.2.0), requiring users to update their dependency declarations. This release introduces new utility functions for HTTP instrumentation, including \extract\_client\_info\, \extract\_scheme\, and \extract\_server\_info\ for parsing request headers according to semantic conventions, as well as \extract\_headers\_attributes\ for mapping selected headers to attribute maps. The library also exposes \normalize\_header\_name\ and \parse\_forwarded\_header\ for common header manipulation tasks.
_utilities/otel\http · high confidence
Test coverage
Added comprehensive test suite for the Cowboy HTTP instrumentation; Added integration and unit tests for Phoenix and LiveView instrumentation; Added test coverage for the OpenTelemetry Process Propagator; Added test environment configuration and database migration for OpenTelemetry Oban; Added test environment configuration for OpenTelemetry Ecto; Added test infrastructure and helper jobs for Oban OpenTelemetry instrumentation; Added tests for KV source instrumentation and context propagation; Added tests for OpenTelemetry Oban job and plugin instrumentation; Added tests for OpenTelemetry Redix instrumentation; Added tests for OpenTelemetry Redix instrumentation; Initial test coverage for OpenTelemetry Oban instrumentation; Initial test suite for OpenTelemetry Ecto instrumentation; Initial test suite for OpenTelemetry Ecto instrumentation; Initial test suite for OpenTelemetry Tesla middleware; Initial test suite for the OpenTelemetry Req instrumentation plugin.
Dependencies
Updated example apps and instrumentation libraries to align with OpenTelemetry 1.7 and semantic conventions v1.27
The example applications (basic\_elixir, basic\_phoenix\_ecto, roll\_dice) and instrumentation libraries (opentelemetry\_absinthe, opentelemetry\_bandit) have been updated to use OpenTelemetry core version 1.7 and the opentelemetry\_exporter version 1.11. The Phoenix and Ecto example now explicitly depends on opentelemetry\_semantic\_conventions \~\> 1.27, and the Absinthe instrumentation has been updated to support Absinthe 1.12 while also adopting the 1.27 semantic conventions. Additionally, the roll\_dice\_elli JavaScript example has been updated to use OpenTelemetry JS packages (api, exporter-trace-otlp-http, etc.) and esbuild/htmx dependencies.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 72 → 79 (+7.0)
- Rubric changed (rubric-2026.11.1 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 67 → 95 (+27.9)
- Architecture 97 → 97 (+0.0)
- Maturity 70 → 71 (+1.3)
- Readiness 76 → 83 (+7.0)
- Security 82 → 81 (-0.8)
Resolved (15)
- Leaked secret: hardcoded-credential (instrumentation/opentelemetry_ecto/config/test.exs)
- Leaked secret: high-entropy-secret (examples/basic_phoenix_ecto/config/dev.exs)
- Leaked secret: high-entropy-secret (examples/basic_phoenix_ecto/config/test.exs)
- Leaked secret: high-entropy-secret (examples/roll_dice/config/dev.exs)
- Leaked secret: high-entropy-secret (examples/roll_dice/config/test.exs)
- Leaked secret: signing-key (examples/basic_phoenix_ecto/config/dev.exs)
- Leaked secret: signing-key (examples/basic_phoenix_ecto/config/test.exs)
- Leaked secret: signing-key (examples/roll_dice/config/dev.exs)
- Leaked secret: signing-key (examples/roll_dice/config/test.exs)
- Medium CVE: EEF-[CVE redacted] (instrumentation/opentelemetry_finch/mix.lock)
- Medium CVE: [GHSA redacted] (instrumentation/opentelemetry_grpc/mix.lock)
- Off-boarding risk: anonymized user #1
- Outdated: nimble_options
- Rotate the exposed credentials — git history can't be un-committed
- Secret: generic-api-key (examples/basic_phoenix_ecto/.env)
New (51)
- Edited copies of one member (3 members, 13+ corresponding lines) (instrumentation/opentelemetry_broadway/lib/opentelemetry_broadway.ex)
- Edited copies of one member (3 members, 13+ corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- Edited copies of one member (3 members, 20+ corresponding lines) (instrumentation/opentelemetry_commanded/lib/commanded/aggregate.ex)
- Edited copies of one member (4 members, 27+ corresponding lines) (instrumentation/opentelemetry_commanded/lib/commanded/aggregate.ex)
- Edited copy of a member (10 corresponding lines) (examples/basic_phoenix_ecto/lib/demo_web/live/user_live/form_component.ex)
- Edited copy of a member (10 corresponding lines) (instrumentation/opentelemetry_commanded/lib/commanded/aggregate.ex)
- Edited copy of a member (10 corresponding lines) (instrumentation/opentelemetry_grpc/lib/opentelemetry_grpc/server.ex)
- Edited copy of a member (11 corresponding lines) (instrumentation/opentelemetry_broadway/lib/opentelemetry_broadway.ex)
- Edited copy of a member (11 corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- Edited copy of a member (11 corresponding lines) (utilities/otel_http/src/otel_http.erl)
- Edited copy of a member (12 corresponding lines) (utilities/otel_http/src/otel_http.erl)
- Edited copy of a member (13 corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- Edited copy of a member (2 corresponding lines) (instrumentation/opentelemetry_oban/lib/opentelemetry_oban/job_handler.ex)
- Edited copy of a member (3 corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- Edited copy of a member (3 corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- Edited copy of a member (30 corresponding lines) (instrumentation/opentelemetry_bandit/lib/opentelemetry_bandit.ex)
- Edited copy of a member (37 corresponding lines) (examples/basic_phoenix_ecto/lib/demo_web/telemetry.ex)
- Edited copy of a member (7 corresponding lines) (instrumentation/opentelemetry_grpc/lib/opentelemetry_grpc/client.ex)
- Edited copy of a member (9 corresponding lines) (examples/basic_phoenix_ecto/lib/demo_web/controllers/post_controller.ex)
- Edited copy of a member (9 corresponding lines) (propagators/opentelemetry_process_propagator/lib/task.ex)
- …and 31 more
Changes since last survey
- 14 commits — 9 feature/other, 5 fixes
By area
- examples/basic_elixir — 2 commits
- examples/roll_dice_elli — 2 commits
- instrumentation/opentelemetry_finch — 2 commits
- (root) — 1 commit
- .github/hex-packages.json — 1 commit
- .github/workflows — 1 commit
- instrumentation/opentelemetry_absinthe — 1 commit
- instrumentation/opentelemetry_commanded — 1 commit
- instrumentation/opentelemetry_cowboy — 1 commit
- instrumentation/opentelemetry_oban — 1 commit
- utilities/opentelemetry_telemetry — 1 commit
Notable commits
- fix: fix(deps): update dependency @opentelemetry/exporter-trace-otlp-http to ^0.301.0 (#882)
- fix: fix(deps): update opentelemetry-js-contrib monorepo to ^0.70.0 (#883)
- fix: fix(opentelemetry_absinthe): handle fragments in request selections (#863)
- fix: fix(opentelemetry_cowboy): set error status when cowboy reports an atom reason (#873)
- fix: fix(opentelemetry_oban): omit nil job timestamps instead of crashing in inline mode (#871)
- change: Add GregMefford to Hex publish list for all packages (#874)
- change: chore(deps): update dependency req to v0.7.5 (#878)
- change: chore(deps): update erlang tool constraint to v29 (#884)
- change: chore(deps): update github-actions (#876)
- change: chore(deps): update jaegertracing/jaeger docker tag to v2.23.0 (#880)
- change: chore(deps): update otel/opentelemetry-collector-contrib docker tag to v0.165.0 (#881)
- change: chore(deps): update patch updates (#877)
- change: test(opentelemetry_finch): cover Req responses collected into a collectable (#870)
- change: test(opentelemetry_telemetry): cover setting the current span once the tracer stack is exhausted (#872)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
open-telemetry/opentelemetry-erlang-contrib 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 a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 15 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit e9e66b063cdbf47009aa6993863b9032871b0851 — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.73+preprod-52de90b74216.