Connect OpenStatus

Firefight has a dedicated alert source for OpenStatus. A failing or degraded monitor becomes an alert that resolves when OpenStatus says it recovered.

Set up the Firefight side

Go to Settings → Alert Sources, click Add source, give it a name like “OpenStatus monitors”, and pick the OpenStatus provider. When you create it, Firefight opens the source’s setup. It shows the ingest URL and a Copy token button for the source’s secret token, and the same steps as this page.

Set up the OpenStatus side

1. In OpenStatus, open Notifications and create a notification channel of type Webhook.
2. Paste the ingest URL as its URL.
3. Add a header named X-Firefight-Token holding the token.
4. Open each monitor that should alert, select the channel on its Notifications tab and save.

Requests that fail the check are rejected with 401, and the source’s row in Settings → Alert Sources shows the rejection.

What Firefight reads

Each alert gets these fields, which you can match in your routing rules.

Field	Value
title	The monitor’s name and whether it is failing or degraded
description	The error, status code, latency and the monitored URL
service	The monitor’s name
severity_raw	error or degraded

Firing and resolving

A monitor fires an alert when it errors or is degraded and resolves it when it recovers.

See Grouping & deduplication for how repeat firings collapse into one alert.