The cutover protects a hard deadline and a security boundary, while missing metrics may only appear during an incident.
Security wants the smallest approved collection surface, and reliability wants verified continuity for every critical service.
Who you’d be doing this for
“If a service goes dark after cutover, my incident lead will be staring at an empty dashboard.”
Beatriz Lopez · Site Reliability Engineering Manager
Leads incident response for the Kubernetes services whose critical Prometheus metrics must survive the cutover.
What is at stake
Nineteen of 240 critical metric series are already absent, and another 27 are only machine-flagged. You must weigh the approved collection boundary against the evidence needed to trust incident response after cutover.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- contract exit vs incident-ready telemetry
- data minimization vs critical service coverage
- automated gap signals vs verified acceptance evidence
- cutover certainty vs parallel-run overhead
Why Grafana
Grafana and Prometheus sit at the center of the customer’s migration from self-managed monitoring to managed observability.
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.