Lightning Talk: Semantics Matter! Lessons From Stabilizing OpenTelemetry’s System Conv...
summary
After two years the system semantic conventions reach a process namespace release candidate and the group chooses concrete names and math: CPU time becomes the recommended source while per-core CPU logical number is made opt‑in, and the memory formula change raises reported usage by 7% increase (a more accurate value, not a bug). That forces tooling work — the Collector adds collector attribute filtering so receivers can drop or aggregate attributes — and Elastic uses versioned dashboards to roll out changes without breaking users.
AI-written summary · about
related talks
13mLightning Talk: Taming Metric Cardinality: Practical Cost Reduction Wit...
07mSponsored Keynote: Why Semantic Conventions are OpenTelemetry’s Most Important Con...
32mOpenTelemetry Semantic Conventions and How to Avoid Broken Observability
06mProject Lightning Talk: OTel 2025: The Latest Milestones and What’s Next
10mLightning Talk: Is OpenTelemetry Too Complicated to Get Started?
05mProject Lightning Talk: New Frontiers for OpenTelemetry - A Roadmap for the Future
17mLightning Talk: Avoiding Chaotic Dysfunction: The ‘Don’t Do This’ Guide T...
04mOpen Telemetry Project Updates