Overview

Send SpeedCurve performance budget alerts to Callgoose SQIBS. A SpeedCurve webhook posts to your SQIBS API endpoint when a budget is crossed, and SQIBS opens an incident named after the chart.

You need
A SpeedCurve account with a site set up, and a SQIBS API token
Setup time
About 10 minutes
Result
Crossed performance budgets open SQIBS incidents

How it works

SpeedCurve
Alert fires
A metric crosses its performance budget.
SpeedCurve
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
The incident takes its title from the chart.

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. In Select Integration Template, choose SpeedCurve. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "message_type" INFO Opens an incident.
Title from "chart"."title" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

SpeedCurve does not send a message when a metric is back within budget, so close these incidents in SQIBS once performance is back.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

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 SpeedCurve

  1. In SpeedCurve, open Settings and scroll to Alerts. Click Add Webhook.
  2. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=speedcurve&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 Webhook, then Add.

Step 3: Set a performance budget

  1. Open a chart (for example in Favorites) or add one, then click Set a Performance Budget.
  2. Choose the metric and the threshold, and keep Send alerts when this threshold is crossed selected.
  3. Save.

Step 4: 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. Click Test Webhook, or set a budget the site already crosses.
  2. In SQIBS, a new incident opens, titled with the chart. SpeedCurve's payload looks like this (shortened):
{
  "message_type": "INFO",
  "chart": {
    "title": "Page Load | AVG",
    "chart_type": "timeseries"
  },
  "budget": {
    "metric": "Page Load",
    "threshold": "4 seconds",
    "threshold_absolute": 4
  },
  "largest_crossing": {
    "type": "over",
    "threshold": 4,
    "latest_value": 10.06
  }
}

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 SpeedCurve 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 SpeedCurve reports page load over budget, SQIBS can run a workflow that purges and warms the CDN cache for the slow pages.

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: