Skip to content
Erlang/Elixir OpenTelemetry API
Erlang Elixir
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci api initial commit Nov 10, 2019
include remove resource from span record (#12) Jan 12, 2020
src remove baggage. it was removed from otep-66 (#9) Jan 10, 2020
.gitignore Initial Elixir API (#3) Jan 8, 2020
CODEOWNERS add CODEOWNERS file (#15) Jan 16, 2020
LICENSE Initial commit Nov 9, 2019 update readme to describe use of api application Nov 10, 2019
VERSION Initial Elixir API (#3) Jan 8, 2020
mix.exs Initial Elixir API (#3) Jan 8, 2020
mix.lock Initial Elixir API (#3) Jan 8, 2020
rebar.config api initial commit Nov 10, 2019

Erlang OpenTelemetry API

This is the API portion of OpenTelemetry for Erlang and Elixir applications.

This is a library, it does not start any processes, and should be the only OpenTelemetry dependency of Erlang/Elixir applications.

The end user of your application can then choose to either include the OpenTelemetry implementation application. If the other application is not in the final release the OpenTelemetry instrumentation will all be noops. This means no processes started, no ETS tables created and nothing added to the process dictionary.

This separation is done so you should feel comfortable instrumenting your Erlang/Elixir application with OpenTelemetry and not worry that a complicated dependency is being forced on your users.

You can’t perform that action at this time.