Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

Robusta logo

Get phone and SMS alerts fromRobusta

Robusta enriches Kubernetes alerts and sends them to the tools you choose. Spike turns every Robusta finding into an incident and pages the engineer on call — by phone, SMS, Slack, or email — escalating until someone picks it up.

Set up with AI

I use Robusta for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a Robusta integration in Spike, copy its webhook URL, and add that webhook to Robusta alert settings. Then help me send a test alert to confirm incidents show up in Spike.

What is Robusta?

Robusta is an open-source platform that sits beside Prometheus in a Kubernetes cluster. When an alert fires, it adds context about the pod, deployment, or node involved and forwards the finding to the sinks you configure. Out of the box that means a Slack channel, which is fine while someone is watching and useless at 3am.

Routed to Spike, each finding becomes an incident instead: the engineer on call gets a phone call and an SMS within seconds, and an unacknowledged alert climbs the escalation policy until a human answers. The incident is titled with Robusta’s own sentence about the fault where it has one, then with the alert’s summary, and only when both are missing with the rule and the namespace, resource, and cluster where it fired, so whoever is looking at a phone screen knows what broke before opening anything.

Robusta identifies each alert with a fingerprint. Repeats of the same alert join the open incident as events rather than paging the team again, and when Prometheus reports the problem resolved, Robusta sends a recovery and Spike closes the matching incident for you. Findings that come from the Kubernetes API rather than Prometheus do not send a recovery, so resolve those by hand. Which clusters and namespaces page which on-call rotation is decided in Spike, where alert rules read each finding before it reaches anyone. The same grouping applies to Prometheus and the rest of your infrastructure monitoring. The full sink configuration is in the Robusta setup guide.

How to set up Robusta alerts

Every Spike integration is a unique webhook URL. Paste it into Robusta and alerts start flowing — no agents, no code.

  1. Step 1: Create a Robusta integration in Spike

    In your Spike dashboard, open Integrations and choose Robusta. Spike generates a unique webhook URL for this integration — copy it.

  2. Step 2: Add a webhook sink in Robusta

    In your Robusta Helm values, add a webhook_sink under sinksConfig with a name, the Spike webhook URL as its url, and format: json, then run helm upgrade to apply it. The format line matters: Robusta's default is plain text, which Spike cannot read, so every alert would arrive with no details and land on one incident. Spike's Robusta guide on docs.spike.sh has the full YAML.

  3. Step 3: Keep the fingerprint in the payload

    Spike uses the alert's fingerprint to join repeats to the open incident and to close it on recovery. If you set size_limit on the sink, leave it large enough that the fingerprint is not cut from the body.

  4. Step 4: Send a test alert

    Trigger a test alert from your cluster, or wait for the next real one, and confirm it opens an incident in Spike within seconds and pages whoever is on call.

That's it — Robusta alerts now page whoever is on call.

More integrations

Explore other tools that plug into Spike the same way.

Try the world’s easiest way
to manage incidents

Start a 14-day free trial. No credit card required.

Spike incident timeline showing an alert escalating through on-call responders

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh