### Component(s) _No response_ ### What happened? **Describe the bug** <!-- A clear and concise description of what the bug is. --> Metric `otelcol_exporter_queue_batch_send_size_bytes` is described as: https://github.com/open-telemetry/opentelemetry-collector/blob/91ba72118c1e38f5bd171c6f3bffcc8aa88582b9/exporter/exporterhelper/internal/metadata/generated_t
> ℹ️ **Note** > > This PR body was truncated due to platform limits. This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.<br>[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/open-telemetry/opentelemetry-collector)
#### Description Record `otelcol_exporter_queue_batch_send_size` and `otelcol_exporter_queue_batch_send_size_bytes` after batching, in the obs report sender, so they reflect the size of the batch actually sent downstream rather than the size of each request at the time of enqueue. #### Link to tracking issue Fixes #14674 #### Testing Moved the existing per-s
### Component(s) exporter/exporterhelper ### What happened? **Describe the bug** With `sending_queue.sizer: bytes` on the Kafka exporter, a collector's memory grew to ~200GB RSS / ~368% CPU when Kafka was slow but alive (backpressure, not an outage — no errors, no rejections). We are seeing multiple collectors start to show this and consume more resources on
### Component(s) _No response_ ### Describe the issue you're reporting Following on #13380, now that we build AIX, this issue is to track moving to tier 2. ### Tip <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context
While reviewing #15756, I noticed that the behavior for component status was changed in #14638, but the documentation is out of date. They should be updated to describe the current behavior.
#### Description Profiles.MergeTo remaps entries from the source dictionary into the destination dictionary but never reserves index 0 of each destination table for that table's zero value. profiles.proto requires that "the element at index 0 MUST be the zero value for the dictionary's element type" (e.g. "" for string_table), since every unset reference (e.
#### Description Currently, if one element from the batch is bigger than the allowed batch size, the full batch is dropped. After this PR, we only drop the "offending" element. <!-- Issue number if applicable --> #### Link to tracking issue Fixes #14264 #### Testing - Manual and unit testing - Added some benchmarking. No regressions found.
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This change involves removing a TODO on timestamp removal, according to discussions in issue #10763. <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation add
This commit addresses several minor issues across the codebase: - connector: Removed duplicate `Consumer` and `PipelineIDs` methods from `logsRouter` that shadowed the embedded `BaseRouter` methods. This also resolves a variable shadowing issue where `var errors error` shadowed the imported `errors` package. - service/internal/graph: Fixed grammatically inco
#### Description Per RFC 7231 3.1.2.2, `Content-Encoding: identity` is a valid header value that signifies no encoding/compression was used. The `httpContentDecompressor` previously rejected payloads with `Content-Encoding: identity` with a `400 Bad Request` because `"identity"` was not registered in the available decoders. This PR fixes the issue by mapping
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description move useProtoPooling feature gate to beta <!-- Issue number if applicable --> #### Link to tracking issue Related to #13631 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describ
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Enables interfaces to validate certificates against configured CRLs, helping ensure that revoked certificates are identified and rejected during certificate validation. <!-- Issue number if applicable --> #### Link to t
#### Description The `memory_limiter` processor currently reports a `StatusOK` event on every memory check while memory usage remains below the soft limit. Since `CheckMemLimits()` runs periodically, this can generate repeated health status events even when the component remains in the same healthy state. This changes the recovery path so that: - `StatusReco
#### Description AddrConfig.Listen() now automatically manages the full lifecycle of filesystem-based Unix domain sockets: - Removes stale socket files before binding (refuses to remove non-socket files for safety) - Sets socket permissions to 0722 so any local process can connect - Cleans up socket files on Close() - Abstract sockets (@ prefix) are unaffect
#### Description Updates the `collection_interval` documentation to match the current implementation. While investigating #15718, I found that the controller uses `collection_interval` to schedule scrapes, while the optional `timeout` field controls the scrape context deadline. The existing timeout tests also verify this behavior. This PR updates the metadat
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR fixes issue with running config generator on subpackage (`metadata.yaml` with `parent` defined but without `status`), but properly building schema title. <!--Authorship attestation. See AGENTS.md for details. AI
#### Description While reviewing #15756, I noticed that the behavior for component status was changed in #14638, but the documentation is out of date. This PR updates them to describe the current behavior. #### Link to tracking issue Fixes #15758 #### Authorship - [x] I, a human, wrote this pull request description myself.