Story
How Spotify Runs Production Support on Grafana
Spotify, a communication services organization in Sweden, uses Grafana from Grafana Labs to support production support for SREs and developers.
Spotify standardized application health on Grafana Labs instead of keeping parallel copies.
“Communication Services work at Spotify spans more than one site, even when headquarters sits in Sweden.”
“SREs and developers asked for a shared way to run production support without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | SREs and developers work from the same Grafana record for application health |
| Capability | Application health can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for application health |
Story
Communication Services work at Spotify spans more than one site, even when headquarters sits in Sweden. Application health was splitting across regional habits. SREs and developers asked for a shared way to run production support without freezing local judgment.
Grafana Labs (Grafana) is what they standardized on. Grafana Labs builds open observability software for dashboards, logs, traces, and metrics, with Grafana Cloud as the hosted option. Spotify uses it as the system of record for application health, with SREs and developers as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.