Story
Splunk
CooperCompaniesCooperCompanies Adopts Splunk for Incident Management
CooperCompanies, a health care organization in the United States, uses Splunk Observability from Splunk to support incident management for on-call rotations.
CooperCompanies folded Splunk Observability into incident management so on-call rotations share one view of on-call response.
“In the United States, on-call rotations already knew where on-call response went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.”
“Splunk (a Cisco company) is a data platform for security and observability, used to search machine data and investigate incidents.”
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 | Splunk Observability is the governed place on-call rotations use for incident management |
| Capability | New joiners can see how incident management actually runs |
Story
CooperCompanies did not need another dashboard that nobody opened. It needed incident management to move. In the United States, on-call rotations already knew where on-call response went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.
Splunk Observability from Splunk is now in that path. Splunk (a Cisco company) is a data platform for security and observability, used to search machine data and investigate incidents. The company treats it as production tooling for incident management, which is why on-call rotations live in it rather than exporting from it once a quarter.
CooperCompanies can show how on-call response is handled today. That is the value: a repeatable way to run incident management on software the rest of the industry already recognizes.
