OpenTelemetry Collector core v1.68.0/v0.162.0 shipped September 28, 2026, and its changelog reads like a Tuesday: a processor rename, a config-key migration, some performance work. Three of those items deserve more attention than the release title gives them, because one of them is a data-loss bug in the batching path that logs pipelines could hit for months without noticing, one is a default flip in HTTP connection behavior across every receiver and exporter in your fleet, and one is a rename that will fail your Collector at startup — no deprecation warning, no alias, no grace period. This is the analysis for operators who ship otelcol to production, not people who collect release notes.

Context for versioning newcomers: the open-telemetry/opentelemetry-collector repo (the core, where this release lives) publishes as two coordinated numbers — the semantic core API version (v1.68.0) and the component-carrying distribution version (v0.162.0). The prebuilt otelcol and otelcol-contrib binaries come from the opentelemetry-collector-releases repo, whose v0.162.0 binaries followed a day later. If you build your own distribution with the Collector Builder (ocb) — and most serious deployments do — the rename in this release is the first thing your build manifest will reject.

The Rename That Fails Your Build: queuebatch → queue_batch

PR #16018, authored by @andrzej-stencel and merged September 24, renames the queuebatch processor component to queue_batch, closing issue #14396 ("Rename components to match naming convention"). The Go package name stays processor/queuebatchprocessor; what changes is the component type: you write in YAML and the name ocb resolves in your builder manifest. There is no compatibility alias, and that is deliberate: the PR body points at the project's own component-naming guideline and notes the component is still Development stability, so the maintainers chose not to preserve the old name.

Before anyone shrugs: the queue_batch processor is not a toy. It re-exports the exact same Config struct as the exporter-side queue helper (exporterhelper.QueueBatchConfig — verified in processor/queuebatchprocessor/config.go in the v0.162.0 tree), which means it gives you the full partitioned-batching engine — metadata_keys partitioning, LRU partition cache, byte-sizing — as a processor, in front of any exporter, including ones with no native partition support. If you were using it to partition logs by tenant before a fan-out exporter, your pipeline definition now contains a component name that v0.162.0 refuses to start. The migration is one line:

# v0.161.0 and earlier                    # v0.162.0
processors:                                processors:
  queuebatch:                                queue_batch:
    batch:                                    batch:
      flush_timeout: 200ms                      flush_timeout: 200ms
      min_size: 8192                            min_size: 8192

service:                                   service:
  pipelines:                                 pipelines:
    logs:                                      logs:
      processors: [queuebatch]                  processors: [queue_batch]