Integration
StackSpend + incident.io
Cost anomalies as incident.io alerts, routed your way.
HTTP alert source · about 3 minutes to set up
What it's for
StackSpend sends anomalies to an incident.io HTTP alert source with a deduplication key and thirteen cost fields, so your existing alert routes decide who gets paged.
On-call docsWhat you get
Rich alerts
Provider, service, expected and actual spend, and deviation arrive as fields your routes can match on.
Your routing, unchanged
incident.io decides who is paged and when, exactly as it does for every other alert.
Two-way with a read key
Add a read-scoped API key and resolving the alert in incident.io closes the anomaly in StackSpend.