WarnFire 1.0 documentation · Pre release

Turn an alarm into a coordinated response.

Build the on-call path, connect the monitoring alarms and alerts that should page it, and run an incident from first notification to resolution.

New to WarnFire? Follow Getting started to build the responder-to-service paging path in dependency order. If that path already exists, connect another service or run the readiness test .

Watch scheduled jobs with Heartbeats , or share customer-facing service health and updates with Status pages .

Start here

Configure a workspace response path and verify the first page.

Understand how events become incidents and how WarnFire keeps one operational record.

Configure schedules and escalation, then coordinate responders through resolution.

Connect monitoring systems through supported, provider-specific webhook adapters.

Monitor scheduled jobs, inspect run output and messages, and investigate failed or overdue runs.

Publish customer updates, manage public and private pages, and pause monitoring for planned maintenance.

Ingest canonical events and build safe, tenant-scoped read automation.

Administer people, services, operating behavior, plans, allowances, and credits.

Learn how WarnFire isolates tenants and distinguishes provider handoff from verified delivery.

Diagnose ingestion, paging, mobile, and integration problems.

Move from Opsgenie with a rehearsed cutover and a working rollback.