Topic starter
19/08/2026 3:55 pm
TL;DR: Exploding observability costs, inconsistent data quality, and brittle OpenTelemetry pipelines that break under change define a telemetry problem in KubeCon North America conversations, according to Sawmills. The practical implication is that teams need upstream control over telemetry volume, schema quality, and pipeline reliability before cost and signal loss become structural.
Editorial analysis by NHI Mgmt Group, based on content published by Sawmills: “KubeCon NA recap. Insights on observability cost, telemetry quality and pipeline innovation”.
Key questions
Q: How should teams reduce observability costs without losing useful telemetry?
A: Start at the pipeline, not the backend.
Q: Why do telemetry pipelines fail when teams make small configuration changes?
A: They fail because the pipeline often behaves like a deployable component rather than a continuously running control layer.
Q: What signals show that data governance is not actually working?
A: Common warning signs are repeated manual rework, conflicting metrics across departments, slow approvals, and frequent disputes about what a data element means.
Practitioner guidance
- Define upstream telemetry policy controls Set explicit rules for what logs, metrics, and traces are collected, enriched, sampled, or dropped before data reaches storage.
- Instrument schema validation and quality checks Detect missing fields, inconsistent attributes, and noisy event patterns before they spread into downstream dashboards and automations.
- Reduce collector change blast radius Use configuration paths that support live updates for processors, filters, samplers, and transformers without forcing collector restarts.
Bottom line: Observability problems are increasingly driven by excess telemetry, poor data quality, and fragile pipeline operations rather than by dashboards alone.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:32 pm
Telemetry sovereignty is becoming a governance problem, not a tooling preference. Once teams depend on upstream control over what gets collected, filtered, and transformed, observability stops being a passive feed and becomes an actively governed data product. That shifts the centre of gravity from dashboards to the pipeline itself, where reliability and policy enforcement have to be managed together. Practitioners should treat pipeline ownership as part of operational control, not just observability engineering.
A question worth separating out:
Q: What should teams do when telemetry changes risk interrupting production data flow?
A: Treat the change as a continuity problem and require a reconfiguration path that preserves live data flow. The goal is to update processors, filters, samplers, and transformers without breaking the collector’s ability to receive and forward telemetry. If that is not possible, the pipeline is too brittle for the environment it supports.
👉 Read our full editorial: Telemetry cost and pipeline fragility are outpacing observability teams