← All digest issues
Observability16 Nov 20263 min read

Observability digest — week of 16 Nov 2026

KubeCon week: the OTel Collector deprecates its batch processor, JS SDK 3.0 and Prometheus 3.16 ship, and AI-driven RCA and agent telemetry mature.

KubeCon North America in Salt Lake City set the pace this week. OpenTelemetry published migration-heavy news for Collector and JavaScript users, and engineering teams kept putting AI to work on root-cause analysis and on instrumenting AI agents. This issue also picks up two notable releases that landed just after the last one.

Releases

  • Deprecating the Collector Batch Processor — OpenTelemetry blog. The batch processor is deprecated in favour of exporter-level batching via sending_queue (or the new queue_batch processor). Exporter batching becomes the default around v0.171.0 and the processor is removed around v0.177.0. Read it for the queue-sizing gotcha: the queue now holds unbatched requests, so the default queue_size can hold far less data than before.
  • Announcing the OpenTelemetry JavaScript SDK 3.0 — OpenTelemetry blog. SDK 3.0 removes deprecated packages such as the Jaeger exporter and the OpenTracing/OpenCensus shims, adds dual ESM/CommonJS exports, and marks Logs stable. The API package has no breaking changes, but the minimum is now Node.js 22.15, so check your runtimes before you upgrade.
  • Prometheus 3.16.0 — GitHub. This release adds experimental query cost estimation and execution limits (--enable-feature=query-cost) and an experimental integral() function. Smoothed and anchored vector selectors are now stable. It also fixes out-of-order sample loss after WAL checkpoints and several OTLP exemplar bugs.
  • Meet the new Elastic Streams: managed data pipelines for telemetry — Elastic Observability Labs. Elastic presents Streams as a managed pipeline layer for routing and processing telemetry, including data arriving via S3. It’s worth a look if you’re weighing vendor-run pipelines against running your own Collector fleet.

Deep dives

Incidents

  • Microsoft 365 outage: timeline, failure mode and incident response breakdown — Xurrent. A breakdown of the Exchange Online degradation that began on 12 November. Servers failing health checks were pulled from rotation, the rest overloaded, and restored capacity buckled under the backlog. Microsoft hasn’t published a root cause yet, but the lessons on readiness checks versus liveness checks, capping health-check ejections, staged recovery and retry budgets apply widely.

Industry news

— END OF ISSUE —More issues →