Get phone and SMS alerts fromOpsPilot
OpsPilot, formerly FusionReactor Cloud, monitors your servers and applications and fires alerts when a rule's condition is met. Spike turns each OpsPilot alert into an incident and pages whoever is on call — phone call, SMS, Slack or email — escalating until someone acknowledges.
Set up with AI
I use OpsPilot for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a OpsPilot integration in Spike, copy its webhook URL, and add that webhook to OpsPilot alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is OpsPilot?
OpsPilot is the cloud monitoring service formerly known as FusionReactor Cloud. Its alert rules watch the instances you monitor and raise an alert when a reading crosses a threshold, such as CPU staying high for several minutes.
On its own, an OpsPilot alert lands in an inbox that is easy to miss outside working hours. Sent to Spike, the same alert becomes an incident: it rings the engineer who is on call, and if nobody acknowledges it, the escalation policy hands it to the next responder.
Spike identifies the alert group by the notification’s groupKey. Repeat notifications for the same group, including new instances that fire in it, join the incident that is already open instead of paging again, and the group’s resolved notification closes it. If you want one incident per host, add the host label to the notification policy’s Group by setting. The incident title is usually the summary from your rule; when several alerts fire in one notification, it counts them and names the rules instead. The rule name and instance travel with it for alert routing rules.
How to set up OpsPilot alerts
Every Spike integration is a unique webhook URL. Paste it into OpsPilot and alerts start flowing — no agents, no code.
Step 1: Create an OpsPilot integration in Spike
In your Spike dashboard, open Integrations and choose OpsPilot. Spike generates a unique webhook URL for this integration — copy it, and attach the integration to the service and escalation policy that should answer OpsPilot alerts.
Step 2: Add a webhook contact point in OpsPilot
In OpsPilot, go to Alerting > Notifications, open the Contact Points tab and click + New contact point. On the Webhook tab choose Webhook, paste the Spike URL, name it and click Save contact point. If the form has a Message setting, set it to {{ .CommonAnnotations.summary }} so the incident title is your rule's summary.
Step 3: Route your alerts to the contact point
On each alert rule, under Then notify, click + Add contact point and choose it, or add a route for it on the Notification Policy tab. When a rule fires, the alert appears in Spike as an incident within seconds, and resolves when OpsPilot reports recovery.
That's it — OpsPilot alerts now page whoever is on call.
