Overview
Send Google Cloud Monitoring alerts to Callgoose SQIBS. A webhook notification channel posts each alerting policy incident to your SQIBS API endpoint. SQIBS opens an incident when Cloud Monitoring opens one and resolves it when Cloud Monitoring closes it.
How it works
open opens it, closed 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 GoogleCloud. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "incident"."state" |
open |
Opens an incident. |
| Resolve | "incident"."state" |
closed |
Resolves the open incident. |
| Match | "incident"."resource_id" |
Ties the resolve message to the incident it opened. | |
| Title from | "incident"."summary" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template matches on "incident"."resource_id", so two policies alerting on the same resource share one incident. Change Map incident with (trigger and resolve) to "incident"."incident_id", which Cloud Monitoring keeps from open to closed.
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 notification channel
- In the Google Cloud console, open Monitoring > Alerting and click Edit notification channels.
- In the Webhook section, click Add new. Enter your SQIBS endpoint as the Endpoint URL and a display name, for example
Callgoose SQIBS:
https://<your-endpoint>/sqibs-api/v1/process?from=googlecloud&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.
- Click Test connection, then Save.
Step 3: Use the channel in alerting policies
In each alerting policy, add the Callgoose SQIBS channel under Notifications and keep Notify on incident closure on, so SQIBS receives the closed message.
Step 4: 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 Test connection on the channel, or let a policy fire.
- In SQIBS, a new incident opens, titled with the incident summary. The payload looks like this (shortened):
{
"incident": {
"incident_id": "0.opqiw61fsv7p",
"state": "open",
"policy_name": "VM CPU high",
"condition_name": "VM Instance - CPU utilization",
"resource_id": "11223344",
"resource_name": "web-01",
"summary": "CPU utilization for web-01 is above the threshold of 0.9 with a value of 0.95.",
"url": "https://console.cloud.google.com/monitoring/alerting/incidents/0.opqiw61fsv7p",
"started_at": 1764000000
},
"version": "1.2"
}
- When the condition clears, Cloud Monitoring sends
"state": "closed"for the same incident, and SQIBS resolves it.
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 Cloud Monitoring channel.
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 Cloud Monitoring reports high CPU on a VM, SQIBS can run a workflow that restarts the runaway service on it.
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.