Skip to main content
Use the Site24x7 Webhooks third-party integration to send monitor status changes to Flashduty On-call. Each Site24x7 monitor maps to one Flashduty alert: a change to Down, Trouble, or Critical triggers or updates the alert, and a return to Up closes it.

​
In Flashduty On-call

You can get the integration push URL in either of the following ways.

​
Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select Site24x7 and click Save
  4. Open the generated integration card and copy the Push URL

​
Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select Site24x7 and enter an integration name
  3. Configure the default route and select a channel. After creation, you can add more rules under Routes
  4. Click Save and copy the generated Push URL

​
Configure site24x7

1

Add a Webhooks integration in Site24x7

Where: Site24x7 › Admin › Third-Party Integrations › Integrations › Webhooks › Integrate NowIf integrations already exist, click + (Add Third-Party Integration) first to open the list, then select Webhooks.
2

Set the request method and body

Where: Site24x7 › Admin › Third-Party Integrations › Integrations › Webhooks (same form)
Select both Post as JSON and Send Incident Parameters. Flashduty rejects a request that lacks STATUS, or lacks MONITOR_ID when MONITOR_DASHBOARD_LINK does not contain a monitor ID either, because later status changes and the recovery could not be linked to the same alert.
3

Choose monitors and trigger statuses

Where: Site24x7 › Admin › Third-Party Integrations › Integrations › Webhooks (same form)Then click Save.
4

Verify the alert lifecycle

Where: Site24x7 › Admin › Third-Party Integrations › Integrations › Webhooks › Save and TestPut a monitor into Down for real, for example by pointing it at an unreachable address for a while, and confirm that Flashduty receives an active alert. Then let it return to Up and confirm that the same alert recovers. The test alert sent by Save and Test only proves that the push URL is reachable. Use a real monitor status change to verify that alerts group and recover correctly.
The test alert is a DOWN notification for a fixed sample monitor (MONITOR_ID 123456, named [Site24x7 Test Alert] Zylker Monitor), so Flashduty opens a Critical alert for it. Site24x7 never sends an Up notification for this monitor, so close that alert in Flashduty manually.

​
Alert key

Flashduty uses the Site24x7 monitor ID as the Alert Key. It takes MONITOR_ID first and, when that is missing, extracts the ID from MONITOR_DASHBOARD_LINK (for example .../home/monitors/<monitor ID>/Summary). The Down, Trouble, Critical, and Up notifications of one monitor all carry the same monitor ID, so they are grouped into the same alert and the Up notification recovers it. Changes to STATUS, the monitor name, the incident reason, the failed locations, or the time do not change the Alert Key.

​
Status and severity

Requests with an empty STATUS are rejected.

​
Alert labels

Flashduty writes the following incident parameters to alert labels for filtering and troubleshooting: The alert title comes from MONITORNAME and the alert description from INCIDENT_REASON.

​
Troubleshooting

  • Site24x7 reports an integration failure: Make sure the Hook URL is complete, includes integration_key, and uses POST
  • Flashduty returns a parameter error: Make sure Post as JSON and Send Incident Parameters are both selected and the request body contains MONITOR_ID and STATUS
  • The alert does not recover: Make sure the monitor is within the scope selected in Integration Level and has actually returned to Up
For parameter details, see the Site24x7 Webhooks integration and Incident Parameters pages.