A renewal decision is forcing managed observability against self-operated control.
Finance wants a predictable ceiling while platform engineering wants ownership of the stack and security wants durable boundaries.
Who you’d be doing this for
“Finance wants a number this week, and my engineers are already pricing the people we’d need to run it ourselves.”
Boris Dabrowski · Head of Site Reliability Engineering
He sponsors the customer’s observability operating model and must justify the path to engineering, security, and finance.
What is at stake
Loki volume is up 46% quarter over quarter, and projections place spend above the approved ceiling. You need to weigh a durable managed adoption case against a self-operated path that gives the customer more direct control.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- managed operational relief vs self-operated control
- spend predictability vs telemetry coverage
- customer urgency vs verified assumptions
- security approval vs adoption speed
Why Grafana
Mimir, Loki, Tempo, and Pyroscope offer the same open-source foundations customers may choose to operate themselves.
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.