OTel Drops: Hostmetrics and model traces

Changing metric conventions can break a dashboard. Exporting model traces can expose only part of a request. This week’s OTel Drops, dated October 19, 2026, looks at two efforts to make telemetry more useful across those boundaries: versioned process metrics in the OpenTelemetry Collector and connected model traces from the Claude Platform.

Hostmetrics moves process metrics toward stable conventions

Collector Contrib v0.160.0 introduced release-candidate (RC) process metrics in the hostmetrics process scraper. The obstacle was preserving existing measurements while introducing changed names, units, types, and attributes. The Collector’s metric code generator, mdatagen, now accepts versioned definitions such as process.cpu.utilization@v1. That suffix distinguishes definitions internally and disappears before export. The hostmetrics migration write-up explains how two feature gates separately enable the new output and disable the legacy output, without rewriting existing metric configuration.

Comparing both outputs has limits: when only attributes change under the same metric name, emitted data points carry both old and new attribute names; a changed metric type uses the new type. Collector v0.163.0 also fixes the final migration state: enabling both gates emits only the new metric and its new attributes. These process metrics are RC, not stable. Test the migration against existing dashboards before adopting it; the source article describes the gates, conflict warnings, and renamed measurements to inspect.

Claude connects model calls to application traces

Anthropic’s public beta brings OpenTelemetry trace export to the Claude Platform. The API and SDK tracing documentation describes two complementary paths: an administrator configures a platform export destination, while SDK instrumentation creates spans inside the application. Together, trace context links client and platform work into the same trace. The spans use generative AI semantic conventions, giving compatible backends a shared vocabulary for model calls and token usage.

That illustrates the producer-side argument in OTel-Native by Design: instrument the product, preserve standard semantics, and let users choose their destination. It also connects to our earlier article, OTLP support is not OpenTelemetry support. Speaking the OpenTelemetry Protocol (OTLP) is only part of the contract. The beta’s boundaries matter too: delivery is best effort, so traces are not a complete usage ledger. Metadata-only capture is the default; enabling full content sends prompts and responses to the destination’s access and retention controls.

Quick hits

• Governance Committee election: Ten candidates are standing for four seats. Check the candidate statements and election schedule. Voter exemption requests close October 23 at 23:59 Anywhere on Earth (AoE); voting runs October 26 at 12:00 UTC through October 28 at 23:59 AoE. Results follow October 30.
• A shared SDK underneath language APIs: The SDK wrapper proposal starts with Python over a C++ SDK. It explores lower allocation costs and less contention on Python’s global interpreter lock. It remains a proposal, rather than a replacement for native SDKs.
• Collector v0.163.0: Profiles version metadata lets the receiver reject unsupported formats before decoding. Custom distributions can also select a smaller set of resource detectors through the builder.
• .NET SDK 1.20.0: The release adds ConfigureSampler, letting library authors work with the application’s resolved sampler, plus improved self-diagnostics and a fix for default resource environment variables.
• OpenTelemetry eBPF Instrumentation approaches 1.0: The project uses extended Berkeley Packet Filter (eBPF) technology for instrumentation. v1.0.0-rc.2 continues the release-candidate cycle. The second-generation configuration is the proposed stable contract; test changed span names and labels against dashboards before the final release.

Community updates

OpenTelemetry Community Awards nominations close October 30. Nominate up to five contributors whose work helped you this year. The new Humans of OpenTelemetry: KubeCon Japan edition shares practitioners’ experiences from Yokohama, with English translations of the Japanese interviews. For anyone looking for a way to join in, OTel in Practice: How can I contribute to OTel? explores that question.

Looking ahead, Observability Day takes place November 9 in Salt Lake City, alongside KubeCon + CloudNativeCon North America, November 9–12, 2026.

OTel Drops is produced by Telemetry Drops, curated by Juraci Paixão Kröhling, and sponsored by OllyGarden. The podcast is largely AI-generated with human curation. Juraci serves on the OpenTelemetry Governance Committee.