Story
Grafana Labs
TapestryTapestry Uses Loki for On-call Response
Tapestry, a consumer discretionary organization in the United States, uses Loki from Grafana Labs to support incident management for on-call rotations.
Tapestry runs incident management on Grafana Labs so ownership is obvious when work stalls.
“On-call rotations needed a system that would still make sense after the original project team moved on.”
“Grafana Labs builds open observability software for dashboards, logs, traces, and metrics, with Grafana Cloud as the hosted option.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in incident management sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Loki is the governed place on-call rotations use for incident management |
| Capability | New joiners can see how incident management actually runs |
Story
Inside Tapestry, incident management used to depend on whoever still had the latest file. That pattern is common in consumer discretionary groups working out of the United States. On-call rotations needed a system that would still make sense after the original project team moved on.
Tapestry uses Loki from Grafana Labs as the working layer for on-call response. Grafana Labs builds open observability software for dashboards, logs, traces, and metrics, with Grafana Cloud as the hosted option. The practical change is simple: incident management has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Tapestry gets from Grafana Labs is a durable place to run incident management and a way for on-call rotations to see the same on-call response at the same time.
