Connect Better Stack
Firefight has a dedicated alert source for Better Stack. Each Better Stack incident becomes an alert that resolves in Firefight when the incident is resolved.
Set up the Firefight side
Section titled “Set up the Firefight side”Go to Settings → Alert Sources, click Add source, give it a name like “Better Stack uptime”, and pick the Better Stack 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 Better Stack side
Section titled “Set up the Better Stack side”- In Better Stack, open Incidents → Integrations, and under Exporting data configure Outgoing webhooks. Add an Incident webhook.
- Paste the ingest URL as the Webhook URL.
- Send it when an incident is started, resolved and reopened.
- Customize the request template and add a header named
X-Firefight-Tokenholding the token. Leave the request body as it is.
Requests that fail the check are rejected with 401, and the source’s row in Settings → Alert Sources shows the rejection.
What Firefight reads
Section titled “What Firefight reads”Each alert gets these fields, which you can match in your routing rules.
| Field | Value |
|---|---|
title | The monitor’s name |
description | The incident’s cause and the monitored URL |
Firing and resolving
Section titled “Firing and resolving”A started incident fires an alert, and its resolve resolves it. Comments are accepted and ignored.
See Grouping & deduplication for how repeat firings collapse into one alert.