Dated component evidence
OpenTelemetry Collector
A bounded release signal for operators who run the Collector as a sidecar or node-local agent. It separates observed upstream facts from upgrade guidance and does not infer compatibility from an image tag alone.
Observed releasev0.160.0
Published upstreamSeptember 2, 2026
Evidence checkedSeptember 4, 2026 · 14:00 UTC
What was observed
Two upgrade checks worth making.
- Core and contrib: the v0.160.0 release artifact was published on September 2. The official Docker installation page used
otel/opentelemetry-collector:0.160.0when this evidence was checked. - Core configuration: v0.160.0 deprecates flat HTTP keepalive fields in favor of a nested
keepalivesection. The release notes say the old fields still work, but configuring an old field and the new section together is an error. - Contrib configuration: v0.160.0 removes
deployment_name_from_replicasetfrom the Kubernetes attributes processor. The contrib notes say leaving that key in a configuration causes startup to fail.
Operational guidance
Before changing the image tag.
- Identify the exact distribution and current tag in the Sidecar BOM. Core and contrib package different component sets, so their release notes are not interchangeable.
- Search the effective Collector configuration for the keepalive fields named in the core notes. If migrating them, do not leave both old and new forms configured.
- If the workload uses contrib, search for
deployment_name_from_replicasetand remove it before testing v0.160.0. - Validate the candidate configuration and exercise the telemetry paths your workload actually uses before rollout. The upstream notes cannot establish compatibility with your backend, extensions, or local configuration.
Evidence limit: this record confirms published upstream information at the observation time. It does not claim that v0.160.0 is appropriate for a particular workload or that any Collector deployment is secure.
Primary sources