Overview
Send Site24x7 monitor alerts to Callgoose SQIBS. A Site24x7 webhook posts each status change to your SQIBS API endpoint. SQIBS opens an incident when a monitor goes down and resolves it when the monitor is up again.
How it works
DOWN opens it, UP closes it.Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Site24x7. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "STATUS" |
down |
Opens an incident. |
| Resolve | "STATUS" |
up |
Resolves the open incident. |
| Match | "MONITORURL" |
Ties the resolve message to the incident it opened. | |
| Title from | "INCIDENT_REASON" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template opens incidents for DOWN only. To also open them for CRITICAL or TROUBLE, add a filter for each with the same Resolve and Match values.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
In the API Integration window, click the round
{} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.Step 2: Add a webhook in Site24x7
- In Site24x7, go to Admin > Third-Party Integration, click + (Add Third-Party Integration) and choose Webhooks.
- Set Integration Name to
CallgooseSQIBSand HTTP Method to POST. - In Hook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=site24x7&token=<your-token>
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
- Tick Post as JSON and Send Incident Parameters, and in the custom payload use the fields the template needs:
{
"STATUS": "$STATUS",
"MONITORNAME": "$MONITORNAME",
"MONITORURL": "$MONITORURL",
"MONITORTYPE": "$MONITORTYPE",
"INCIDENT_REASON": "$INCIDENT_REASON",
"INCIDENT_TIME": "$INCIDENT_TIME",
"INCIDENT_DETAILS": "$INCIDENT_DETAILS",
"FAILED_LOCATIONS": "$FAILED_LOCATIONS",
"MONITOR_DASHBOARD_LINK": "$MONITOR_DASHBOARD_LINK",
"TAGS": "$TAGS"
}
- Under Trigger Alerts for Monitor Status Change, choose which states to send (Down, Critical, Trouble). Keep Up so incidents resolve.
- Choose the monitors or monitor groups, then click Save and Test.
Step 3: Test it
The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.
- Click Save and Test, or Trigger Test Alert in the Third-Party Integration list.
- In SQIBS, a new incident opens, titled with the incident reason.
- When the monitor is up again, Site24x7 sends
"STATUS": "UP"for the sameMONITORURL, and SQIBS resolves the incident.
No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Site24x7 webhook.
Fix known issues automatically
Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when Site24x7 reports a URL monitor down, SQIBS can run a workflow that restarts the web service and rechecks the page.
Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.
To set it up, in the same API filter:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.
Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.
Learn more:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.