Identity-provider dependence can block the telemetry needed to diagnose the identity failure itself.
Emergency access protects investigation continuity while least privilege protects each tenant’s telemetry boundary.
Who you’d be doing this for
“When sign-in went down, our responders had to wait for an admin while the outage clock kept moving.”
Bora Choi · Platform Security Engineer
Owns access controls for a cloud-native engineering organization that uses Mimir, Loki, and Tempo during critical incidents.
What is at stake
Identity disruption has delayed access to incident telemetry for high-SLA customers. You must weigh recovery speed against tenant isolation and least-privilege controls.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- emergency access vs tenant isolation
- customer self-service vs control simplicity
- cross-product consistency vs narrow first scope
- recovery speed vs privilege durability
Why Grafana
Mimir, Loki, and Tempo hold the metrics, logs, and traces customers need when distributed systems fail under time pressure.
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.