Overview
Send FortiMonitor incidents to Callgoose SQIBS. A webhook integration posts each outage and its clearance to your SQIBS API endpoint. SQIBS opens an incident when FortiMonitor detects an outage and resolves it when the outage clears.
How it works
outage opens it, clear 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 Fortinet FortiMonitor. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "event_trigger_type" |
outage |
Opens an incident. |
| Resolve | "event_trigger_type" |
clear |
Resolves the open incident. |
| Match | "alert_label" |
Ties the resolve message to the incident it opened. | |
| Title from | "event_type" |
Becomes the incident title. | |
| Description from | "incident_reasons" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
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 integration in FortiMonitor
- In FortiMonitor, go to Teams & Activity > Integrations and click Configure under Webhook.
- Give it a title, for example
Callgoose SQIBS, and choose the trigger events Incident detection and Incident closure. - Set Request method to POST and Postback URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=fortimonitor&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.
- Set Payload type to Raw payload, Content type to JSON, and use this payload (it must include
event_trigger_type, which the template uses):
{
"alert_label": "$alert_label",
"event_trigger_type": "$trigger",
"event_type": "$event",
"server_name": "$name",
"server_fqdn": "$fqdn",
"server_group": "$server_group",
"outage_id": "$outage_id",
"incident_reasons": "$reasons",
"incident_severity": "$severity",
"incident_duration": "$duration",
"affected_items": "$items",
"metric_category_name": "$metric_category",
"incident_timestamp": "$timestamp"
}
- Save the integration and add it to the alert timelines of the instances you want in SQIBS.
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.
- Make a check fail, for example a response time threshold the site cannot meet.
- In SQIBS, a new incident opens. FortiMonitor's payload looks like this (shortened):
{
"alert_label": "751",
"event_trigger_type": "outage",
"event_type": "outage event",
"server_name": "shop-web",
"server_fqdn": "shop.example.com",
"incident_reasons": "HTTPS response time greater than 2s for more than 1 minute",
"incident_severity": "critical"
}
- When the outage clears, FortiMonitor sends
"event_trigger_type": "clear"for the samealert_label, 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 FortiMonitor 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 FortiMonitor reports a web service down, SQIBS can run a workflow that restarts it and checks the port answers 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.