Story
PagerDuty
LyftLyft Uses AIOps for Log Investigation
Lyft, an industrials organization in the United States, uses AIOps from PagerDuty to support incident response for on-call engineers.
Shared AIOps workspaces help Lyft keep incident response honest across teams.
“Industrials work at Lyft spans more than one site, even when headquarters sits in the United States.”
“On-call engineers asked for a shared way to run incident response without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because log investigation has a clear owner |
| Productivity | Handoffs in incident response sit in a shared queue instead of a mailbox trail |
| Capability | New joiners can see how incident response actually runs |
Story
Industrials work at Lyft spans more than one site, even when headquarters sits in the United States. Log investigation was splitting across regional habits. On-call engineers asked for a shared way to run incident response without freezing local judgment.
PagerDuty (AIOps) is what they standardized on. PagerDuty is an operations cloud for incident response, on-call, and event intelligence used by digital operations teams. Lyft uses it as the system of record for log investigation, with on-call engineers 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.
