Getting started

Getting started

Configure a complete response path and verify it with a test alarm.

WarnFire turns monitoring alarms into accountable incident response. Your monitoring system sends a trigger event through an integration; WarnFire opens an incident and starts the service’s paging path.

Build a working response path in this order: responder → schedule → escalation policy → service and integration key . A team is optional; use one when responders share schedule ownership or must be targeted as a group.

Before you begin

You need an organization-provisioned workspace and tenant-owner or tenant-administrator access. Ask the workspace owner to add you if you do not already have access. Keep integration keys in a secret manager; WarnFire displays a new key only once.

Set up the complete path

First-run setup creates the responder, schedule, escalation policy, service, and Events API integration together. You do not need to create each record separately.

1. Set up your workspace and sign in.
2. On First-run setup, enter:
   • the first responder’s name and email;
   • the schedule name, timezone, and daily handoff time;
   • the escalation policy name; and
   • the service name.
3. Select Create response path.
4. Copy the integration key immediately and store it securely.
5. Select Send test event.
6. Confirm that WarnFire opens the test incident and pages the scheduled responder.

The test follows the real ingest and escalation path and can page an on-call responder.

Add another response path

Create the records in dependency order:

1. Add the responder .
2. Optionally create a team for shared ownership or all-member paging.
3. Create the schedule and add the responder to its rotation.
4. Create the escalation policy and target that schedule.
5. Create the service and integration key and select that policy.
6. Send a trigger event and verify the resulting incident.

Connect your monitoring system

Choose the provider-specific webhook adapter for your monitoring system, or use the Events API directly.