Lightning Talk: Taming Metric Cardinality: Practical Cost Reduction Wit...
summary
Shows how the OpenTelemetry Collector plus OTTL rules cut explosive metric cardinality (examples show up to a million potential time series) and can cut backend cost and noise — one case cites ~30% savings after semantic conventions. Practical steps: standardize tags, use the transform and filter processors to rename or drop user/host IDs, aggregate with telemetry-to-metric pipelines, test with OTTL.Run and synthetic load from telemetrygen, validate configs with otelbin, and deploy via an OpAMP control plane.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:02What is metric cardinality
- 3:36OpenTelemetry Collector solution
- 5:01Five steps to tame cardinality
- 6:48Transforming telemetry with OTTL
- 7:52Filtering useless telemetry
- 8:33Aggregating metrics to reduce noise
- 10:17Testing and deploying safely
- 12:24Summary
related talks
11mLightning Talk: “Metrics That Lie”: Understanding OpenTelemetry’s Cardinality Capping...
12mLightning Talk: With Great Traces Comes Great Costs: How to Reduce That Bill?- 12mLightning Talk: With Great Traces Comes Great Costs: How to Reduce That Bill?
30mPanel: Telemetry That Matters
24mScaling Telemetry To Terabytes: Applying Google's Principles To OpenTelemetry...
10mLightning Talk: Semantics Matter! Lessons From Stabilizing OpenTelemetry’s System Conv...
06mObservability Diet: Your 5-Step Plan To Trim the Data Fat
02h 41mThe Science of Signals: Mastering Telemetry for Observability