OpenTelemetry Deprecates Span Events API in Favor of Log-Based Events
OpenTelemetry is deprecating the Span Events API to eliminate confusion and unify event handling through log-based events correlated with spans.
OpenTelemetry is deprecating the Span Events API to eliminate confusion and unify event handling through log-based events correlated with spans.
Key portions of the OpenTelemetry declarative configuration specification have been marked stable, including the JSON schema, YAML representation, and SDK operations for parsing and instantiation.
The KubeCon + CloudNativeCon India 2026 schedule is less interesting as an event announcement than as a demand signal. AI + ML, observability, operations, platform engineering, and security are showing up together because teams no longer get to treat them as separate tracks in production.
OpenClaw’s 2026.3.8 release leans hard into operational maturity: first-class backup + verification for local state, optional ACP provenance receipts for traceability, and a raft of reliability fixes across cron delivery, browser relay, and cross-channel routing.
OpenTelemetry’s declarative configuration model just reached a stable milestone. That’s not a cosmetic win — it’s a shift toward consistent, policy-friendly telemetry configuration across languages, SDKs, and (increasingly) the Collector. Here’s what’s stabilized, what’s not, and how platform teams should plan adoption.
Datadog says the next generation of Bits AI SRE is roughly 2× faster, can reason across more telemetry sources, and exposes an “Agent Trace” view to show its tool calls and intermediate steps. This is the right direction — but it also turns agent transparency into an operational requirement, not a nice-to-have.
Collector-contrib v0.146.0 brings OTTL context inference to the Filter Processor, reducing config footguns and making filtering rules more readable. Here’s what changes for platform teams running OTel at scale.
The OpenTelemetry project says key parts of its declarative configuration spec are now stable, including the data model schema and YAML representation. That’s a quiet milestone with big implications: versionable config, safer rollout patterns, and vendor-neutral ‘observability as code.’
Collector-contrib v0.146.0 adds context inference to the Filter Processor, letting teams write readable, intent-first OTTL conditions instead of juggling internal contexts. Here’s what changes, how evaluation works, and how to adopt it safely.
OpenTelemetry’s eBPF Instrumentation project shipped its first alpha release. Here’s what you gain (and what you still don’t) when you shift observability left—down into the kernel.
OpenTelemetry’s eBPF instrumentation (OBI) is now shipping an initial release, pushing the ecosystem toward low-friction, kernel-level telemetry—especially for large fleets where manual instrumentation doesn’t scale. Here’s what eBPF-based signals are good for, where they’re risky, and how to roll them out safely in production.
OpenTelemetry’s eBPF Instrumentation project (OBI) just hit its first release. That’s a milestone for low-overhead, zero-code observability—but it also raises new questions about privilege, fleet rollout, and data governance.
Logs are expensive because repetition is free to emit and costly to store. The OTel Collector’s log deduplication processor offers a new middle path: compress noise at ingest while preserving incident context.
OpenTelemetry is now mainstream, and the project’s own ‘2025 year in review’ highlights a less-discussed scaling story: documentation localization, contributor growth, and the operational maturity required when observability becomes an industry baseline.
A quiet but important trend: vendors are shifting OpenTelemetry collector distribution to CDNs. That changes reliability, patch velocity, and how platform teams should govern observability agents.
The Collector is easy to deploy but surprisingly easy to misconfigure at scale. This guide focuses on the practical knobs—pipelines, batching, tail sampling, memory limits, and auth—to turn ‘telemetry works’ into ‘telemetry is reliable.’
KubeCon + CloudNativeCon Europe heads back to Amsterdam on March 23–26, 2026. Here’s a practical preview of the themes to track—platform engineering, security, observability, and AI—and how to get more value out of the week.
Cilium 1.18.7 adds pragmatic improvements—safer default label handling and better Hubble Relay logging options—plus bugfixes that matter in real clusters. Here’s what to pay attention to and how to roll it out without surprises.
Envoy Gateway v1.7 lands with a dense set of Gateway API-adjacent upgrades: richer policy controls, better OTLP export options, safer extension defaults, and breaking changes that signal maturity.
OpenTelemetry adoption is running into a new bottleneck: operating collector fleets. IBM Instana just made OpAMP-powered fleet management generally available, highlighting a shift from ‘instrumentation’ to ‘collector ops’ as the next maturity step.