Overview

Send pgDash PostgreSQL alerts to Callgoose SQIBS. A webhook integration posts each alert, and each recovery, to your SQIBS API endpoint. SQIBS opens an incident when an alert rule triggers and resolves it when the rule clears.

You need
A pgDash account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
pgDash alerts open and resolve SQIBS incidents

How it works

pgDash
Alert fires
An alert rule triggers (for example replication lag).
pgDash
Sends a webhook
Through a webhook integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
trigger opens it, resolve 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 pgDash template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "action" resolve Resolves the open incident.
Trigger "action" trigger Opens an incident.
Match "alert_rule"."id" Ties the recovery to the incident it opened.
Title from "alert_rule"."name" Becomes the incident title.
Description from "text" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The old version of this page resolved on a status key that pgDash does not send; both filters use "action". If one rule watches several servers, check in the API log whether the server name should be part of the match.

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 integration in pgDash

  1. In pgDash, open the integrations settings, choose Add Integration > Webhook.
  2. Set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=pgdash&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. Save, then add the integration to your Alert Rules.

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 the test option on the integration, or let a rule trigger.
  2. In SQIBS, a new incident opens. The payload looks like this:
{
  "type": "alert",
  "action": "trigger",
  "text": "Replication lag is high on prod-db-01",
  "alert_rule": {
    "id": 12345,
    "name": "High replication lag"
  },
  "server": {
    "name": "prod-db-01"
  }
}
  1. When the rule clears, pgDash sends "action": "resolve" for the same rule, 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 pgDash integration.

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 pgDash reports long-running queries blocking others, SQIBS can run a workflow that lists the blockers and cancels the ones your rules allow.

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: