Overview

Send Embrace alerts to Callgoose SQIBS. Embrace posts each alert state change to a webhook. SQIBS opens an incident when an alert moves to Error and resolves it when it returns to Normal.

You need
An Embrace app with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Embrace alerts open and resolve SQIBS incidents

How it works

Embrace
Alert fires
A metric alert moves to Error.
Embrace
Sends a webhook
Through a webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Error opens it, Normal 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

  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 Embrace template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event"."metric_props"."new_state" Error Opens an incident.
Trigger "event"."metric_props"."new_state" Warning A second filter, so warnings open incidents too (optional).
Resolve "event"."metric_props"."new_state" Normal Resolves the open incident.
Match "alert"."id" The alert's id: the same for every state change of one alert.
Title from "alert"."name" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Do not match on "event"."id": every state change has a new event 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 the webhook in Embrace

  1. In the Embrace dashboard, open Settings > Integrations > Webhooks and add a webhook.
  2. Give it a name and enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=embrace&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. Click Test to check the connection.
  2. Open Alerts, create or edit an alert, and under Send to Webhooks choose the webhook. 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.

  1. Use Test on the webhook, or lower an alert's threshold so it fires.
  2. In SQIBS, a new incident opens. Embrace's payload looks like this (shortened):
{
  "version": "1.0",
  "alert": {
    "id": "8vOXjpQ",
    "name": "Network request errors",
    "type": "metric"
  },
  "app": {
    "name": "Shop App",
    "platform": "Web",
    "environment": "Production"
  },
  "event": {
    "id": "vrAmRqN",
    "type": "metric",
    "metric_props": {
      "old_state": "Normal",
      "new_state": "Error",
      "value": "4.000"
    }
  },
  "links": {
    "dashboard_url": "https://dash.embrace.io/app/..."
  }
}
  1. When the alert recovers, new_state is Normal 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 Embrace 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 Embrace reports a spike of failed network requests from the app, SQIBS can run a workflow that checks the API gateway and restarts the unhealthy backend.

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: