Overview
Send MongoDB Cloud Manager alerts to Callgoose SQIBS. Cloud Manager manages MongoDB deployments that you run yourself; a webhook notifier on any of its alerts posts to your SQIBS API endpoint.
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.
- In Select Integration Template, choose MongoDB Cloud Manager. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "status" |
informational |
Opens an incident. |
| Title from | "eventTypeName" |
Becomes the incident title. | |
| Description from | "humanReadable" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template matches informational events ("status" contains informational), such as a user joining the project. For host and metric alerts, which arrive as OPEN and CLOSED, use the values of the MongoAtlas - Host template instead (trigger OPEN, resolve CLOSED) and map on "id".
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 notifier to a Cloud Manager alert
- In Cloud Manager, open the project and go to Alerts. Click Add New Alert, or edit an existing one.
- Choose the category and condition.
- Under notifications, click Add Notifier and choose Webhook. Enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=cloudmanager&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 the alert.
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.
- Trigger the condition, for example by inviting a test user to the project for a user alert.
- In SQIBS, a new incident opens. The payload looks like this (shortened):
{
"id": "66f228c58613c02cbf0a18ff",
"alertConfigId": "66f0f4331a51b73e34dba847",
"eventTypeName": "JOINED_GROUP",
"status": "INFORMATIONAL",
"humanReadable": "User joined the project"
}
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 Manager notifier.
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 Manager reports a host down, SQIBS can run a workflow that restarts the mongod service on that host and checks the replica set status.
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.