Incident response
Turn monitoring alerts into on-call paging with clear escalation and live context.
High error rate
api.prod.example.com
ALERT
Page on-call
Primary: Alex Chen
Notifying
Incident response, job monitoring, and status pages.
Connect monitoring alerts and missed check-ins to on-call paging, Slack or Zoom war rooms, and clear customer updates.
-
High error rate api.prod.example.comALERT
-
Page on-call Primary: Alex Chen
Respond within 5 minutes -
Open Slack war room #incident-api
-
Publish customer update We're investigating increased errors.
Heartbeats
Monitor scheduled jobs and services with expected check-ins and automatic missed check-in detection.
Expected check-in
scheduler.daily-report
On time
Missed check-in
scheduler.daily-report
Overdue
War rooms
Create a dedicated war room in Slack or Zoom for each incident. Choose the provider that fits your team.
Open a Slack war room
#incident-api
Open a Zoom war room
Incident: API outage
Status pages
Write and publish clear, customer-facing updates during an incident.
Write update
We’re investigating increased errors and will share an update shortly.
Publish to customers
Alertmanager, Grafana, Datadog, CloudWatch, Azure Monitor, and Google Cloud can keep detecting problems. WarnFire receives their alerts, identifies the responsible service, and runs its response plan.
See supported integrations- Prometheus Alertmanager
- Grafana Alerting
- Datadog
- Amazon CloudWatch
- Azure Monitor
- Google Cloud Monitoring
- Nagios & Icinga
- Events API & webhooks
Make the response plan clear before you need it.
Connect the system that needs attention to the people responsible for it. Each part has a specific job, and each incident keeps the response plan captured when it opened.
-
Services define ownership.
Give the Payments API its own service, monitoring credentials, and escalation policy.
-
Schedules resolve coverage.
Use rotations, overrides, cover, and swaps to identify who is on call when the incident opens.
-
Policies control the response.
Choose people or teams, severity, channels, response windows, and the next escalation step.
The incident, its context, and your next action.
Acknowledge from iPhone, iPad, or Android. Review incident activity, ask a specialist for help, open the selected Slack or Zoom war room, and keep your on-call commitments in view.
Plan the move from Opsgenie.
Assess users, teams, schedules, policies, and services before changing a paging path. Review mappings and gaps, then cut over service by service.
Build a response people can follow.
Start a workspace, connect a service, and make the next signal reach its owner.