Overview
Send Hexowatch change alerts to Callgoose SQIBS. Hexowatch watches web pages for visual, content, HTML and availability changes and can call a webhook when it finds one. SQIBS opens an incident for each change, titled with the monitor name.
How it works
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.
- Add a filter with these values (there is no built-in Hexowatch template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "monitoredUrl" |
Opens an incident for every change. | |
| Title from | "name" |
The monitor name. | |
| Description from | "link" |
A link to the comparison in Hexowatch. |
- Choose the Priority for these incidents and click Save.
Each change is its own event, so there is nothing to resolve: close the incident once you have checked the change. To watch one site only, put its domain in Key value contains.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 the webhook in Hexowatch
- In Hexowatch, open Settings > Integrations (webhooks) and add your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=hexowatch&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.
- Turn the webhook on for the monitors you want in SQIBS (in each monitor's notification settings).
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 Run now on a monitor whose page has changed.
- In SQIBS, a new incident opens. The payload looks like this (shortened; check yours in the API log):
{
"id": "chg_123456789",
"title": "Visual monitoring change detected",
"name": "Homepage visual check",
"monitoredUrl": "https://www.example.com",
"changePercentage": "15",
"link": "https://hexowatch.com/monitor/123/comparison/456"
}
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 Hexowatch 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 Hexowatch sees a defaced or broken home page, SQIBS can run a workflow that redeploys the last good release of the site.
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.