Alex Morgan · Principal Engineer
Alex Morgan is a principal engineer at SyncRivo, focused on platform architecture, reliability engineering, and the infrastructure powering real-time messaging interoperability. LinkedIn
April 9, 2026 · 10 min read
Route Prometheus AlertManager firing alerts to every platform your SRE and engineering teams use — simultaneously. One webhook_config entry. Fan-out to Slack, Teams, Webex, and more.
Add a SyncRivo webhook_config receiver to your alertmanager.yml:
receivers:
- name: 'syncrivo-fanout'
webhook_configs:
- url: 'https://hooks.syncrivo.ai/webhook/YOUR_ENDPOINT'
send_resolved: true
route:
receiver: 'syncrivo-fanout'
# Or route specific labels:
routes:
- match:
severity: critical
receiver: 'syncrivo-fanout'SyncRivo fans this single webhook out to Slack, Teams, Webex, Google Chat, and Zoom based on your configured channel mappings.
All AlertManager webhook event types are accepted — firing alerts, resolutions, grouped batches, and Grafana Alertmanager webhooks.
AlertManager firing groups routed to SRE Slack channels and engineering Teams channels simultaneously in real time.
Alert resolution events broadcast to incident channels so stakeholders know the issue is cleared automatically.
Critical alerts fan out to Slack and Teams simultaneously. Warning alerts route to team channel only — configurable per label.
AlertManager grouped alert batches delivered as a single notification to avoid notification storms in messaging channels.
SyncRivo routes only alerts AlertManager has determined should fire — inhibition rules are respected automatically.
Grafana-managed alerts (Grafana 8+ built-in Alertmanager) routed identically to standalone Prometheus AlertManager alerts.
Setup takes under 15 minutes. Requires access to your alertmanager.yml.
Example routing for SRE teams using Prometheus in multi-platform engineering organizations.
| AlertManager Event | SyncRivo Routes To | Result |
|---|---|---|
| severity=critical firing | → Slack #sre-alerts + Teams #engineering-incidents | SRE and leadership notified immediately |
| severity=warning firing | → Slack #sre-alerts | Team channel only — no leadership escalation |
| alert resolved (status=resolved) | → All subscribed channels | All-clear broadcast confirms issue cleared |
| grouped alert batch (3 alerts) | → Slack #sre-alerts | Single grouped notification — no notification storm |
| Grafana Alertmanager webhook | → Slack + Teams simultaneously | Identical routing works for Grafana-managed alerts |
| team=payments firing | → Slack #payments-sre + Teams #payments-eng | Team-scoped routing via label matching in SyncRivo |
Prometheus AlertManager has a built-in Slack receiver. In your alertmanager.yml, configure a receiver with the slack_configs section, providing your Slack webhook URL or API token and a channel name. For routing the same AlertManager alert to Slack AND Teams simultaneously, SyncRivo accepts the Alertmanager webhook payload and fans it out to all connected messaging platforms.
AlertManager does not have a native Teams receiver. The standard approach is to use the "webhook_configs" receiver in AlertManager pointing to a service that translates and forwards to Teams. SyncRivo acts as that relay: configure an AlertManager webhook_config pointing to your SyncRivo endpoint, and SyncRivo routes the alert to Teams (and simultaneously to Slack, Webex, Google Chat, or Zoom) automatically.
AlertManager natively supports multiple receivers and routing rules — you can route different alert labels to different Slack channels. For routing a single alert to BOTH Slack AND Teams (or other platforms) at the same time, SyncRivo acts as a fan-out layer: one AlertManager webhook_config → SyncRivo → all connected platforms simultaneously, no additional AlertManager receiver configuration needed.
Configure an AlertManager webhook_config pointing to your SyncRivo inbound webhook endpoint. In SyncRivo, map the AlertManager source to all your destination platforms (Slack, Teams, Webex, Google Chat, Zoom) with routing rules per alert severity or label. One webhook_config entry in AlertManager — fan-out to all platforms.
Yes. SyncRivo accepts the standard AlertManager webhook payload format (application/json with "alerts" array, "commonLabels", "commonAnnotations", "groupKey", and "status" fields). No custom configuration needed in AlertManager — use the standard webhook_configs receiver type with your SyncRivo endpoint URL.
Yes. Grafana's built-in Alertmanager (used for Grafana-managed alerts in Grafana 8+) sends webhooks in the same format as the standalone Prometheus AlertManager. Configure a Grafana webhook contact point pointing to SyncRivo — the routing, fan-out, and platform delivery work identically.
SyncRivo receives the AlertManager webhook payload after AlertManager has applied grouping and inhibition — so SyncRivo only routes alerts that AlertManager has decided should fire. SyncRivo does not re-implement AlertManager logic. Each webhook call from AlertManager (a group of alerts) is routed as-is to your configured messaging destinations.
Free plan available. No credit card required. One webhook_config — all your platforms.
Ready to connect? Slack ↔ Teams connection setup →