opentelemetry-erlang-contrib
opentelemetry-erlang-contrib copied to clipboard
OpenTelemetry instrumentation for Erlang & Elixir
Using the `Finch.stream/5` function fails with a `%KeyError{}` and detaches the :request_stop telemetry handler. **Expected behavior** A clear and concise description of what you expected to happen. I've tracked it...
Maybe this context should be set on start event, but it was called on stop event. https://github.com/open-telemetry/opentelemetry-erlang-contrib/blob/c8b760e77601a66e20041957d5c102f455fa71d5/instrumentation/opentelemetry_cowboy/src/opentelemetry_cowboy.erl#L53 My spans are shown in two different like this:  I want that...
Tracking which Semantic Conventions couldn't be replaced to figure out what the path forward will be with them: ## Redix - [ ] ["db.redix.connection_name"](https://github.com/open-telemetry/opentelemetry-erlang-contrib/blob/01fc804ab2347568e4fe6f7de79e6400d5a5b023/instrumentation/opentelemetry_redix/lib/opentelemetry_redix.ex#L88) ## Phoenix - [ ] ["phoenix.plug"](https://github.com/open-telemetry/opentelemetry-erlang-contrib/blob/d1ec189362b34d198a641144eee259d83c4fdb64/instrumentation/opentelemetry_phoenix/lib/opentelemetry_phoenix.ex#L151)...
We now have https://hex.pm/packages/opentelemetry_semantic_conventions which is generated from the spec semantic conventions https://github.com/open-telemetry/opentelemetry-specification/tree/main/semantic_conventions yaml All the existing libraries must be updated to use these macros for attribute keys instead of...
Similiar to https://github.com/open-telemetry/opentelemetry-erlang-contrib/pull/205 empty stack happens in pop_from_tracer_stack function Having not this case handled is causing telemetry handler to detach It originated from opentelemetry_cowboy, Stack: ``` Telemetry handler failed: %{reason:...
[](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [opentelemetry_process_propagator](https://hex.pm/packages/opentelemetry_process_propagator) | minor | `~> 0.2.1` -> `~> 0.3.0` | --- ### Configuration...
**Describe the bug** * Dependency resolution fails when doing step 2. of the example. ``` > mix deps.get, ecto.setup Resolving Hex dependencies... Resolution completed in 0.277s Because the lock depends...
**Describe the bug** The docker setup for the example `basic_elixir` seems to fail. With `docker-compose up` in the current `main` branch, both the `elixir` container and the `otel` container stop...
The link in the README.md for conventions used in OpenTelemetry traces leads to a 404 page: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/README.md