The collection path must stop duplicate logs without disturbing existing clusters.
New cluster accuracy pulls against preserving the Grafana Alloy settings already running in customer environments.
Who you’d be doing this for
“I opened the incident logs and every restart looked like it happened twice.”
Defne Esfahani · Site Reliability Engineer
Runs Kubernetes services and uses Loki during production incident response.
What is at stake
Eighteen percent of newly enrolled clusters are sending duplicate container logs into Loki, and your fix decides whether those users can trust their incident searches. You must protect existing collector deployments while restoring logs that SREs can rely on.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast relief vs source-level correction
- new-cluster accuracy vs existing configuration stability
- clear onboarding vs added validation steps
- query cleanliness vs ingestion cost
Why Grafana
Kubernetes Monitoring Helm Chart collection is the entry point for customers who expect managed telemetry to work on the first deployment.
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.