opentelemetry-collector
opentelemetry-collector copied to clipboard
open-telemetry
OpenTelemetry Collector
### Component(s) ALL ### What happened? See statements like `replace go.opentelemetry.io/collector/pipeline => ../` ### Collector version v0.126.0
- This change modifies the persistence strategy to write all relevant queue information (start, stop, in-progress, size) together under a single key on every write operation. - This ensures a...
The merge of https://github.com/open-telemetry/opentelemetry-collector/pull/10160 causes issues w/ gogenerate
### Component(s) exporter/exporterhelper ### Describe the issue you're reporting If #12934 is landed, this will store spanContext for internal batch tracking span/telemetry as JSON in persistent storage. But since we...
**Describe the bug** If the Collector emits two internal metric streams which differ only by their instrumentation scope attributes, the [Prometheus exporter from the Go SDK](https://github.com/open-telemetry/opentelemetry-go/tree/main/exporters/prometheus) —which is the default...
**Describe the bug** We are currently using the OpenTelemetry Collector to log telemetry data into a logfile. The logfiles are continuously growing, and we encounter issues when the pod gets...
### Component(s) exporter/exporterhelper ### Describe the issue you're reporting It seems that `internal/queuebatch` package is growing rather large and interdependent. Given comments on #12934 (https://github.com/open-telemetry/opentelemetry-collector/pull/12934#discussion_r2101353533), it could be worthwhile to...
The data types changes in OTLP 1.7.0 make the batcher upgrade non-trivial. So we have decided to disable batching for profiles with the upgrade. See https://github.com/open-telemetry/opentelemetry-collector/pull/13075 We should add that...
**Is your feature request related to a problem? Please describe.** #8804 proposing tracing the consumer in order in order to have tracing across all components. This does not cover receivers....
