Alertmanager fires.
Runframe incident exists.
Add a webhook receiver to your Alertmanager config. When an alert fires, Runframe creates an incident, maps your labels to severity and service, and pages the on-call engineer.
How it works
One receiver block. Nothing to install.
Add the Runframe webhook URL to Alertmanager
Copy your service webhook URL from Runframe and add it as a receiver in your Alertmanager config. Route the alerts you want to the new receiver.
Alerts fire, incidents are created automatically
When Alertmanager fires a notification, Runframe receives the payload and creates an incident. The on-call engineer is paged immediately via Slack DM and email.
Labels map to severity and service
Runframe reads your severity and service labels from the alert payload and applies them directly to the incident. No manual triage needed to get the right context.
What you get out of the box
Runframe uses everything Alertmanager sends.
Severity label mapping
The severity label on your alert maps to Runframe incident severity. Critical becomes SEV0, warning becomes SEV2, info becomes SEV4. Configurable per service if your labels differ.
Service label correlation
Runframe reads the service or job label and correlates the incident to the matching Runframe service. On-call schedules, escalation policies, and notification rules all apply automatically.
Alert grouping and deduplication
Runframe deduplicates by alert fingerprint. If the same alert fires again while an incident is open, it updates the existing one instead of creating a duplicate.
Works with any Prometheus-compatible stack
Thanos, Cortex, and Mimir all use the same Alertmanager webhook format. If it speaks Alertmanager, it works with Runframe. No special configuration.
Label mapping
Prometheus labels become Runframe incident fields.
Runframe reads standard Prometheus labels from the Alertmanager webhook payload. No custom configuration required for the common case.
| Prometheus label | Runframe field | Notes |
|---|---|---|
severity | Incident severity | critical → SEV0, warning → SEV2, info → SEV4 |
service / job | Service | Matched against your Runframe service list by name |
alertname | Incident title | Used as the incident title when no summary annotation is present |
summary (annotation) | Incident title | Takes precedence over alertname when present |
description (annotation) | Initial context | Added to the incident timeline as the first entry |
All mappings are configurable per service. If your team uses different label names, you can override them in the Runframe service settings without changing your alert rules.
Frequently asked questions
Prometheus is already alerting. Make those alerts actionable.
Start free. Connect Alertmanager in under 5 minutes.