opentelemetry-erlang-contrib
opentelemetry-erlang-contrib copied to clipboard
OpenTelemetry instrumentation for Erlang & Elixir
It's not always necessary/desired to include this attribute, especially as in some cases it can be very long.
**Is your feature request related to a problem? Please describe.** LiveView can be very noisy, and the current implementation of `opentelemetry_phoenix` currently only supports enabled/disabled (I believe). **Describe the solution...
The main purpose of this patch is to introduce plugin aware attributes - mostly counts of processed jobs. Plugins cover all the offerings of Oban 2.15 and Oban Pro 1.0,...
The Semantic Conventions spec introduced a significant breaking change (opinion) to the HTTP Tracing spec's span name conventions in v1.18, along with a number of other breaking changes in v1.20....
At the moment we have 3 HTTP server instumneters (`cowboy`, `phoenix` and `elli`) and 4 HTTP client ones (`finch`, `httpoison`, `req` and `tesla`). They expose some common option, some options...
The main objective of this patch is to add few tests to cover main points of how this library handles OpenTelemetry. As by-product of those tests, few tweaks were done...
Currently `opentelemetry_telemetry` relies on `telemetry_registry` but I am wondering if that's an anti-pattern because that takes control away from users. Instead, we should add a public API to register spans:...
Maybe better to get this configuration parameter from the setup function instead of application env but for now this PR it's a draft waiting for comments. The use case is...
See #183 ~~I implemented this on top of #128 because it was more convenient for me so we should wait for merging that PR before merging this one.~~
### What does this PR do? The Dataloader instrumentation's `[:dataloader, :source, :run, :start]` event handler now first tries to fetch a parent context from `self()` before checking the `:"$callers"`. **Context**...