Get phone and SMS alerts fromNobl9
Nobl9 tracks your service level objectives and alerts you when an error budget is burning faster than it should, or when an SLO stops receiving data. Spike pages a human for it: a phone call, SMS, Slack message or email to whoever is on call, escalating until someone picks it up.
Set up with AI
I use Nobl9 for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a Nobl9 integration in Spike, copy its webhook URL, and add that webhook to Nobl9 alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is Nobl9?
Nobl9 is a service level objective platform. Instead of alerting on raw metrics, it measures how much of an SLO’s error budget is left and alerts when that budget is being spent too quickly — a fast burn that needs a human now, or a slow one that can wait for morning. It also raises a no-data alert when an SLO stops receiving the measurements it depends on.
A Nobl9 alert on its own is an email or a message in a channel. Pointed at Spike through a webhook alert method, it becomes a page: the on-call engineer is called and texted within seconds, and an alert nobody acknowledges climbs the escalation policy until someone answers. The incident’s title is the alert policy’s own description plus the SLO and service it fired on — “Checkout API is burning its error budget more than 5x faster than allowed (checkout-api-availability in checkout)”, say — so whoever wakes up knows what broke and where before opening anything.
Every Nobl9 alert carries a unique ID, so repeats of the same alert stay together as one incident instead of paging the team twice. Who gets paged, and how hard, is decided in Spike: alert routing rules read the severity, SLO, service and project each alert arrives with, so a staging SLO doesn’t wake the same people a production one does.
Nobl9 does not send a recovery to webhooks, so Spike does not close these incidents on its own — resolve them from Spike once the budget is healthy again.
How to set up Nobl9 alerts
Every Spike integration is a unique webhook URL. Paste it into Nobl9 and alerts start flowing — no agents, no code.
Step 1: Create a Nobl9 integration in Spike
In your Spike dashboard, open Integrations and choose Nobl9. Spike generates a unique webhook URL for this integration — copy it, and attach the integration to the service and escalation policy that should answer these alerts.
Step 2: Add a webhook alert method in Nobl9
In Nobl9, add a webhook alert method and paste the Spike URL as the endpoint. The token in the URL is the credential, the same as every other Spike integration.
Step 3: Paste the payload template
Nobl9 lets you define the JSON it posts. Paste Spike's template, which maps Nobl9's own alert variables — the alert ID, alert policy name and description, severity, SLO and service — onto the fields Spike reads.
Step 4: Attach the alert method to an alert policy
Add the alert method to the alert policies that should page someone. When one fires, Spike opens an incident titled with the policy's description and the SLO and service it fired on, so the alert reads on a phone lock screen without opening Nobl9.
That's it — Nobl9 alerts now page whoever is on call.
