Alex Boten
Alex Boten
As identified during the work for #2354, the log emitter provider doesn't have a default or noop implementation.
## Changes The following PR adds a section to the OTLP exporter about setting a user agent. This was implemented in the otel collector and provides users with additional information...
As a result of the discussion in April 19th SIG meeting, it was suggested that it would be useful for debugging purposes that the OTLP exporter add version information to...
Currently Trace/Tracing/Traces, Metrics, and Logging/Logs are used in various places to name the OpenTelemetry signals. It would be great to ensure these are named consistently at least in the status...
Currently the lambda extension described in the readme is published via a Lightstep-owned account, this should be changed to publish the extension from an OpenTelemetry owned AWS account.
As per the specification https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#opentelemetry-protocol-exporter, the environment variable is TRACES, not SPAN.
As per the specification https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#opentelemetry-protocol-exporter, the environment variable is plural.
This change updates the changelog process in this repo to match the process in the contrib repo. Fixes #5647 ~Keeping this as a draft until the next release to avoid...
The HTTP Check Receiver can be used for synthethic checks against HTTP endpoints. This receiver will make a request to the specified `endpoint` using the configured `method`. Fixes #10607
### What happened? ## Steps to Reproduce Using the example code from opentelemetry.io, I tried configuring an endpoint to send data to and was receiving 404's from my backend. After...