opentelemetry-collector icon indicating copy to clipboard operation
opentelemetry-collector copied to clipboard

OpenTelemetry Collector

Results 925 opentelemetry-collector issues
Sort by recently updated
recently updated
newest added

Need to investigate if the current expand providers logic in the [`confmap.Resolver`](https://github.com/open-telemetry/opentelemetry-collector/blob/main/confmap/resolver.go#L168) has all the equivalent functionality. Then we also need to propose some kind of deprecation process: e.g. disable...

### Component(s) receiver/postgresql ### What happened? Password containing `$` doesn't work when passed via `${env:DB_PASSWORD}`. When passed directly, it works. ## Description ## Steps to Reproduce 1. Prepare PostgreSQL DB:...

bug
release:required-for-ga
priority:p2
area:config

Like open-telemetry/opentelemetry-collector#9601, but for v0.100.0 **Performed by collector release manager** - [x] Prepare stable core release v1.7.0 - [x] Tag and release stable core v1.7.0 - [x] Prepare beta core...

release

#### Documentation Creates an internal architecture file. In it is a diagram of the startup flow of the collector as well as links to key files / packages. I also...

Skip Changelog

See the [requirements for receivers here](https://github.com/open-telemetry/opentelemetry-collector/blob/b2961b799e2c1ec128f0539764af1fa10c839e04/receiver/doc.go#L21). OTLP/HTTP receiver needs to: - Return [429 or 503 responses](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlphttp-throttling) on non-permanent errors. - Return [400 response](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#bad-data) on permanent errors. OTLP/gRCP receiver needs to:...

bug

#### Description Documents how we want to configure confmap Providers, with the default decision being to use URI fragments. Per the SIG discussion on 2024-05-08, I have included as many...

**Describe the bug** We noticed that while we rollout new changes on our collector it the applications report some warnning/error on connection refused. Our collector is managed by the Operator...

bug

**Describe the bug** There is a dead link in the mdatagen README page, which no longer links to a page that exists **Steps to reproduce** Visit the [mdatagen readme.md](https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/README.md) Click...

bug

#### Description The current `ConfmapProvider` interface accurately reports the config provided to the Collector by the user, but fails to effectively report the Collector's effective configuration. In particular, it misses:...

**Describe the bug** When having more than one batchers, for example: ```yaml processors: batch/1: send_batch_max_size: 10000 timeout: 10s metadata_keys: ["label1"] metadata_cardinality_limit: 0 batch/2: send_batch_max_size: 10000 timeout: 10s metadata_keys: ["label2"] metadata_cardinality_limit:...

bug