Opened) and closes when the incident closes (Closed).
In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
- In the Flashduty console, go to Channels and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Select Atatus and click Save
- Open the generated integration card and copy the Push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Atatus and enter an integration name
- Configure the default route and pick a channel; add more rules under Routes later
- Click Save and copy the generated Push URL
In Atatus
1
Create a Webhook notification channel in Atatus
Where: Atatus › Alerting › Notification Channels › Create new notification channel
Click Create channel when done.Atatus’s own Webhook integration page also describes a second entry point, Settings › Team Notifications › Webhook (URL only). Both create the same kind of channel; this guide follows Notification Channels.
2
Attach the channel to an alert policy in Atatus
Where: Atatus › Alerting › Alert PoliciesOpen the policy to push, click Add notification channels, and tick the
Flashduty channel and click Add Channels. Atatus notifies the channel when an incident under that policy is opened, closed or acknowledged.3
Send a test notification and verify the lifecycle
Where: Atatus › Alerting › Notification ChannelsOpen the channel you just created and click Send Test Notification. The test notification only proves the URL is reachable: for Atatus’s fixed test text, Flashduty opens a separate Info alert that you close manually; any other request without
incident_id is rejected. It does not prove the alert policy or the recovery flow, so verify with a real alert: trigger an alert rule and confirm Flashduty receives an active alert. After the incident closes in Atatus (or after you change the rule so the condition no longer holds), confirm the alert recovers.Payload
Atatus POSTs these fields asapplication/json. Flashduty parses them directly, with no template to configure:
Other fields, including
target_name, acknowledge_url, account_id, alert_url and timestamp, are not stored.
Alert key
Flashduty usesincident_id as the Alert Key. The open and close notifications of one Atatus incident carry the same incident_id, so they land on the same alert. What counts as one incident is set by the policy’s Incident preference (by policy, by rule, or by rule and target), and Flashduty follows it.
A request without incident_id is rejected with a parameter error, because its close notification could not be matched to the original alert.
Status and severity
A request whose
status is empty or any other value is rejected, so a request of unknown state never lands in the wrong lifecycle.
FAQ
Does acknowledging an incident in Atatus affect the Flashduty alert?
Does acknowledging an incident in Atatus affect the Flashduty alert?
No. Acknowledge notifications are accepted and ignored. Handle the Flashduty alert in Flashduty.
The channel test succeeded, but real alerts do not arrive?
The channel test succeeded, but real alerts do not arrive?
The channel test only checks that the URL is reachable and opens a separate Info test alert. Confirm the alert policy uses the channel, the rule is enabled, and the condition held for the duration the rule requires.
Troubleshooting
- Atatus fails to deliver: confirm the URL is the full push URL and includes
integration_key - Flashduty returns a parameter error: confirm the request has
incident_idand thatstatusisOpened,ClosedorAcknowledged - The alert does not recover: confirm the alert policy still uses the channel; the close and open notifications must carry the same
incident_id