Story
PagerDuty
IterableIterable Uses AIOps for Application Health
Iterable, an information technology organization in the United States, uses AIOps from PagerDuty to support production support for SREs and developers.
Iterable asked for a cleaner operating picture of application health. PagerDuty is what they run.
“Information Technology work at Iterable spans more than one site, even when headquarters sits in the United States.”
“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 | Named workflow replaces ad hoc routing for application health |
| Capability | Production support stays visible to adjacent teams through AIOps |
| Capability | SREs and developers work from the same AIOps record for application health |
Story
Information Technology work at Iterable spans more than one site, even when headquarters sits in the United States. Application health was splitting across regional habits. SREs and developers asked for a shared way to run production support 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. Iterable 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.
