Incident response

WarnFire maintains one incident record from the first trigger through resolution. The overview shows current values, Updates shows how values changed, and Activity records operational actions and notification delivery.

Acknowledgement

Acknowledgement identifies the responder who has taken ownership. It stops further automatic escalation as configured, but it does not resolve the incident. The incident remains open until WarnFire receives a corresponding resolve event or an authorized responder resolves it.

Dynamic assistance

An incident responder can invite another responder or the person currently on call for a team. The invitee receives a push notification containing the incident and request identifiers. They can:

Join immediately.
Commit to join after a stated delay.
Decline and optionally provide a reason.
Leave an incident after joining.
Be requested again later if circumstances change.

Assistance decisions are returned to the incident activity stream so the requesting team can act on them.

Resolution

Resolution closes the incident and records when and how it ended. Where policy requires it, include a human-readable resolution note. A later trigger with the same deduplication identity may create a new incident according to the service’s lifecycle rules.

Incident lifecycleWhat happens from the first alert to the all-clear, and what actually stops the paging.SchedulesSet up who is on call and when, using rotations, layers, and vacation overrides.Escalation policiesDecide who gets paged, in what order, and how long to wait before trying the next person.Response teamInvite experts mid-incident, accept or decline invitations, and hand off cleanly.SlackPost incidents to your channels and let authorized responders acknowledge from Slack.