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 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.
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.’