Service attribution is unreliable, but the control that protects it can interrupt ingestion.
Kubernetes Monitoring needs clear workload identity while the Collector path must not block healthy telemetry at scale.
Who you’d be doing this for
“During the incident, three services appeared as one and everyone chased the wrong owner.”
Gabriel Medina · Platform Engineering Lead
Runs the customer’s Kubernetes telemetry standards and must support SRE incident response.
What is at stake
Twenty-nine percent of affected Kubernetes workloads have conflicting service attribution. You must weigh immediate telemetry continuity against a cutover that makes downstream diagnosis trustworthy.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- telemetry continuity vs service identity
- conservative containment vs durable control
- machine-generated diagnosis vs verified evidence
- Kubernetes visibility vs downstream trust
Why Grafana
Grafana Cloud depends on correctly attributed OpenTelemetry data for Kubernetes Monitoring and Application Observability to deliver meaningful first value.
Written with these in mind
Not your kind of problem? 24 more at Grafana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.