Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 50% off your first six months 

Argo CD logo

Get phone and SMS alerts fromArgo CD

Argo CD keeps your Kubernetes clusters in line with Git. Spike turns failed syncs and degraded applications into incidents, routed to the on-call engineer by phone, SMS, Slack, and email, and closes them when the application recovers.

Set up with AI

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

What is Argo CD?

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. It watches your Git repositories, compares them with what is running in your clusters, and syncs the difference. Each Application reports a sync state and a health state, and Argo CD Notifications can send both to a webhook.

A failed sync or a degraded application can sit unnoticed until a release stalls or a service misbehaves. Connected to Spike, a failed sync or a Degraded health status becomes an incident: the on-call engineer is called, and the alert escalates if nobody responds. Spike tracks each Application by its Kubernetes UID, so repeat notifications join the same incident. When the Application is Healthy again after a successful sync, the incident resolves itself.

How to set up Argo CD alerts

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

  1. Step 1: Create an Argo CD integration in Spike

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

  2. Step 2: Add the webhook service to Argo CD Notifications

    In the argocd-notifications-cm ConfigMap, add a webhook service that points at the Spike URL, and a template that sends status, app, app_uid, health_status, sync_status, operation_phase and operation_message. The Spike guide has the full template.

  3. Step 3: Add triggers and subscribe your applications

    Create triggers for a failed sync, a degraded application, and a recovery, then subscribe your applications to them. Trigger a test notification: it appears in Spike as an incident within seconds.

That's it — Argo CD 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