opentelemetry-erlang-contrib
                                
                                 opentelemetry-erlang-contrib copied to clipboard
                                
                                    opentelemetry-erlang-contrib copied to clipboard
                            
                            
                            
                        OpenTelemetry instrumentation for Erlang & Elixir
Each HTTP client/server instrumentation in this repo needs to add an option for including headers as attributes that follows the semconv: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-spans.md#http-request-and-response-headers
This PR adds a compose file with only the needed dependencies to see the traces of your Elixir project and some documentation around it.
Opening this in hopes there is a kind soul interested in tackling this -- well, first assuming @bryannaegele supports this plan. I'd like publishing to hex done through github actions....
Hello, we've implemented two libraries for OpenTelemetry that we'd like to offer to this project. - [opentelemetry_quantum](https://github.com/breakroom/opentelemetry_quantum): Implements telemetry handlers for the Quantum cronjob library - [opentelemetry_heroku](https://github.com/breakroom/opentelemetry_heroku): Implements a resource...
Assuming this https://github.com/open-telemetry/opentelemetry-specification/pull/3478/files is merged we need to update all the HTTP instrumentation libraries to follow it.
Some other languages' OpenTelemetry HTTP instrumentation libraries provide convenient options for filtering and modifying the spans created by the instrumentation libraries. It would be great to provide these options in...
[ExAws](https://github.com/ex-aws/ex_aws) just merged the necessary telemetry changes that include the AWS service name and operation in the telemetry metadata. It hasn't been included in a published version yet, but I...
**Describe the bug** Maybe not really a bug but more a lack of configuration or adherence to the spec. We're seeing this kind of error: ``` OTLP grpc export failed...
Right now each Instrumentation only uses the global TracerProvider. They need to be able to be configured to use a specific TracerProvider (defined as a pid, registered atom or `{via,...