Overview
Send Semonto alerts to Callgoose SQIBS. Semonto posts a webhook when a test changes status. SQIBS opens an incident when a test is in error and resolves it when it is OK again.
How it works
error opens it, ok 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 Semonto. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "status_str" |
error |
Opens an incident. |
| Resolve | "status_str" |
ok |
Resolves the open incident. |
| Match | "id" |
Ties the resolve message to the incident it opened. | |
| Title from | "tests".[0]."friendly_name" |
Becomes the incident title. | |
| Description from | "tests".[0]."info" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
SQIBS lists two identical Semonto templates; either one fills in these values. Semonto sends ok, warning, critic or error. The template opens incidents for error only; add a second filter with critic to page on critical states too. For a clearer title, change Incident title from to "name" (the monitor name).
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 the webhook in Semonto
- In Semonto, open Notifications and add a notification (or edit one). Choose the tests it covers.
- In the Webhooks section, turn webhooks on and click Add URL.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=semonto&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.
- Save. To apply it to monitors you add later, turn on Default Settings in the General section.
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.
- Send a test message from the webhook settings, or monitor an address that does not answer.
- In SQIBS, a new incident opens. Semonto's payload looks like this (shortened):
{
"id": 17166,
"type": "reachability",
"status_str": "error",
"status": 4,
"name": "shop.example.com",
"tests": [
{
"key": "reachability",
"status": "4",
"info": "1289.7 | http: 503",
"friendly_name": "Reachability (HTTP ping)",
"status_str": "Error"
}
],
"test_date": 1764152021,
"url": "https://shop.example.com"
}
- When the test is OK again, Semonto sends
"status_str": "ok"for the sameid, 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 Semonto 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 Semonto reports a cron job missed, SQIBS can run a workflow that checks the scheduler service and runs the job again.
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.