opentelemetry-collector
opentelemetry-collector copied to clipboard
open-telemetry
OpenTelemetry Collector
**Is your feature request related to a problem? Please describe.** The [Debug exporter](https://github.com/open-telemetry/opentelemetry-collector/blob/v0.103.0/exporter/debugexporter/README.md) implements outputting metric data point as one-liners in https://github.com/open-telemetry/opentelemetry-collector/pull/10462. This PR is missing bucket output for Exponential...
#### Description We have recently discussed bumping the minimum TLS version to follow security best practices. Since we are about to stabilize `configtls` (see #10344), I raised the question of...
During the v0.103.0 release we run into trouble with the builder go releaser setup, which necessitated a v0.103.1 release only for the builder. We should document what the process looks...
#### Description Mark module as stable. #### Link to tracking issue Fixes #9377
**Describe the bug** When we use `pmetric.JSONMarshaler.MarshalMetrics()` function([ref](https://github.com/open-telemetry/opentelemetry-collector/blob/6c2108d0392604475c1b168c82b6a2910cefe461/pdata/pmetric/json.go#L24)) to get JSON string of a `pmetric.Metrics` variable, the generated JSON contains wrong data type used for some of the fields. viz;...
Context: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33539#discussion_r1644122489 When marking all internal metrics as optional, the generated code has a compilation error, as it defines a var (`err`) that ends up not being used.
**Is your feature request related to a problem? Please describe.** The `otlpreceiver` supports gRPC and HTTP. For the gRPC protocol, there is an automatic deadline applied by gRPC itself. For...
**Is your feature request related to a problem? Please describe.** In the OTel-Arrow project, we have identified a [problem where a context originating in a OTel-Arrow receiver stream has no...
**Is your feature request related to a problem? Please describe.** Related to batch sender in #8122 Currently, queue sender and batch sender work together fine, but the config `sending_queue.num_consumers` and...
the OTLP exporter added validation for the endpoint in https://github.com/open-telemetry/opentelemetry-collector/issues/9505, but that configuration uses configgrpc for its endpoint. My question is whether this validation should be moved to configgrpc instead...
