Integration
StackSpend + PagerDuty
Critical cost spikes page whoever is on call.
Events API v2 key · about 3 minutes to set up
What it's for
StackSpend sends critical cost anomalies to a PagerDuty service you choose, de-duplicated so a multi-day spike is one incident, and resolves it when someone resolves the anomaly in StackSpend.
On-call docsWhat you get
One incident per spike
De-duplicated by anomaly, so a spike that runs for three days pages once, not three times.
Your rotation decides
Alerts land on the service you pick and follow its existing escalation policy.
Closes itself
Resolve the anomaly in StackSpend and the PagerDuty incident resolves with it.