Overview

Send Monte Carlo data alerts to Callgoose SQIBS. Monte Carlo posts a JSON webhook for each new alert (freshness, volume, schema, custom rule). SQIBS opens an incident and pages the data on-call team, so data downtime gets the same response as an outage.

You need
A Monte Carlo account with permission to manage notifications, and a SQIBS API token
Setup time
About 10 minutes
Result
Monte Carlo data incidents open SQIBS incidents

How it works

Monte Carlo
Alert fires
A monitor finds a data anomaly or rule breach.
Monte Carlo
Sends a webhook
Through a webhook notification, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Each new alert opens one incident.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in Monte Carlo template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "type" open Opens an incident for new alerts (types such as open_anomaly_incident).
Match "payload"."incident_id" Keeps later messages for the same alert on one incident.
Title from "type" Becomes the incident title (the alert type).
Description from "payload"."event_list".[0]."event_details" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Monte Carlo can also send alert updates, for example when someone marks an alert fixed. To resolve incidents from those, look at an update in the API log and add a Resolve filter on its status field (values such as fixed or no_action_needed), matched on the same incident id.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
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 in Monte Carlo

  1. In Monte Carlo, go to Settings > Notifications and add a Webhook recipient. Name it Callgoose SQIBS.
  2. In the URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=montecarlo&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.

  1. Optionally add a shared secret; Monte Carlo then signs each request (HMAC SHA-512). SQIBS does not need it.
  2. Choose the audiences, domains or tags whose alerts go to SQIBS, and save. Use the test option to send a sample.

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.

  1. Send a test notification, or let a monitor find an anomaly.
  2. In SQIBS, a new incident opens. Monte Carlo's payload looks like this (shortened):
{
  "account": {
    "id": "9a59c6f1-203a-4c72-8cd7-132db7f21b92"
  },
  "action": "incident",
  "payload": {
    "event_list": [
      {
        "event_details": "Has 42 rows vs. 101 expected",
        "table_name": "orders"
      }
    ],
    "incident_id": "f83867b6-8f25-428b-807c-08518f63384c",
    "url": "https://getmontecarlo.com/incidents/f83867b6-8f25-428b-807c-08518f63384c"
  },
  "type": "open_anomaly_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 Monte Carlo 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 Monte Carlo reports a stale table, SQIBS can run a workflow that restarts the failed load job and checks the row count again.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

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:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. 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: