Story
PagerDuty
ResMedResMed Uses AIOps for Application Health
ResMed, a health care organization in the United States, uses AIOps from PagerDuty to support production support for SREs and developers.
ResMed asked for a cleaner operating picture of application health. PagerDuty is what they run.
“SREs and developers needed a system that would still make sense after the original project team moved on.”
“PagerDuty is an operations cloud for incident response, on-call, and event intelligence used by digital operations teams.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | SREs and developers work from the same AIOps 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
Inside ResMed, production support used to depend on whoever still had the latest file. That pattern is common in health care groups working out of the United States. SREs and developers needed a system that would still make sense after the original project team moved on.
ResMed uses AIOps from PagerDuty as the working layer for application health. PagerDuty is an operations cloud for incident response, on-call, and event intelligence used by digital operations teams. The practical change is simple: production support has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What ResMed gets from PagerDuty is a durable place to run production support and a way for SREs and developers to see the same application health at the same time.
