Overview
Send Redgate Monitor database alerts to Callgoose SQIBS. Redgate Monitor posts each alert to your SQIBS API endpoint through a webhook notification. SQIBS opens an incident when an alert is raised and resolves it when the alert ends.
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 Redgate Monitor template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "severity" |
Critical |
Opens an incident. |
| Resolve | "severity" |
Normal |
Resolves the open incident. |
| Match | "alertId" |
Ties the resolve message to the incident it opened. | |
| Title from | "alertName" |
Becomes the incident title. | |
| Description from | "description" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
These values follow the payload shown in the test step. Send one test notification first and confirm the keys with the JSON key creator: Redgate Monitor can change its payload between versions, and SQIBS matches key names exactly (upper and lower case matter). Add one filter per severity you want to page on (for example a second one for High).
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 Redgate Monitor
- In Redgate Monitor, go to Configuration > Notification settings and open the Webhook section.
- Turn webhook notifications on and enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=redgatemonitor&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.
- Send a test notification, then save.
- Under Configuration > Alert settings, choose the alert types that should notify by webhook.
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 the test notification from step 2, or let an alert be raised.
- In SQIBS, a new incident opens. Check the payload in the API log and adjust the filter keys if they differ. A raised alert looks like this (shortened):
{
"alertName": "SQL Server CPU utilization high",
"severity": "Critical",
"description": "CPU utilization above 90% on sql-prod-01",
"alertId": "rg-48213",
"timestamp": "2026-11-22T10:00:00Z"
}
- When the alert ends, the message for the same
alertIdresolves 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 Redgate Monitor 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 Redgate Monitor reports a blocking process on a SQL Server, SQIBS can run a workflow that captures the blocking chain and attaches it to the incident.
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.