Slack
Incident channels, two-way acknowledgement and resolution, and configurable automatic archiving.
Keep the tools that detect problems. Connect what happens next.
Send alerts from your monitoring systems to a WarnFire service. Its on-call schedule and escalation policy decide who responds; Slack or Zoom provides the incident's collaboration space.
Bring your monitoring alerts.
Use the adapter for your source and a dedicated integration key. Confirm the mapping and paging path before depending on it.
| Source | What connects |
|---|---|
| Prometheus Alertmanager | Grouped alerts and their recovery state. |
| Grafana Alerting | Alert groups with dashboard and panel context. |
| Datadog | Monitor alerts and recovery events. |
| Amazon CloudWatch | Alarm changes through SNS or EventBridge. |
| Azure Monitor | Alert and resolution events. |
| Google Cloud Monitoring | Monitoring incident events. |
| Nagios and Icinga | Problems, recovery, and source acknowledgement history. |
| Generic webhook | A provider-neutral JSON envelope. |
| PagerDuty-compatible senders | Events API v2 body shape at a custom WarnFire endpoint. |
Bring the response to Slack or Zoom.
Choose the provider that fits your team. A dedicated war room keeps the conversation tied to the incident rather than a busy general channel.
See how war rooms workZoom
A meeting and private Team Chat channel, incident cards, authorized actions, assistance, and controlled meeting admission.
Connect jobs that need to check in.
Heartbeats covers work that should happen on a schedule. Send a check-in directly or use a client wrapper for cron, systemd, macOS, Windows, Docker, or Kubernetes CronJobs.
Build around the incident lifecycle.
Use the Events API to trigger, acknowledge, and resolve correlated incidents. Use scoped service accounts for automation and lifecycle webhooks for outbound incident events.
Read the product guideScoped credentials
Keep monitoring integration keys attached to their service and alert source. Manage automation credentials separately with explicit access.
Attributable events
Keep automation and responder actions in the incident history. Inspect outbound delivery attempts and failures when another system needs investigation.
Build a response people can follow.
Start a workspace, connect a service, and make the next signal reach its owner.