Get phone and SMS alerts fromHarness FME
Harness FME, formerly Split, runs your feature flags and experiments and alerts you when a metric moves. Spike turns every FME metric alert into an incident, with on-call schedules, escalations, and phone, SMS, Slack, and email alerts.
Set up with AI
I use Harness FME for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a Harness FME integration in Spike, copy its webhook URL, and add that webhook to Harness FME alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is Harness FME?
Harness FME, formerly Split, lets teams roll out features behind flags and measure their impact with experiments. When a key or guardrail metric crosses an alert policy threshold or reaches statistical significance, FME can post a webhook.
Connected to Spike, that webhook becomes an incident that names the metric, the flag or experiment, and the environment. Repeat alerts for the same flag, environment, and metric join the open incident instead of paging again. FME does not send recovery notifications, so you resolve these incidents in Spike yourself.
How to set up Harness FME alerts
Every Spike integration is a unique webhook URL. Paste it into Harness FME and alerts start flowing — no agents, no code.
Step 1: Create a Harness FME integration in Spike
In your Spike dashboard, open Integrations and choose Harness FME. Spike generates a unique webhook URL for this integration — copy it.
Step 2: Add a webhook in Harness FME
In Harness FME, open FME Settings → Integrations, pick Webhooks, and click Add on Outgoing Webhook (Metric Alerts). Choose the project, the environments and the alert types, paste the webhook URL you copied, click Send Test Message, then Save.
Step 3: Send a test alert
Trigger a test message or wait for a metric alert. The alert shows up in Spike as an incident within seconds.
That's it — Harness FME alerts now page whoever is on call.
