Overview

Send Pagescreen visual monitoring alerts to Callgoose SQIBS. When Pagescreen captures a page and finds a change, its webhook posts the details to your SQIBS API endpoint, and SQIBS opens an incident with links to the capture and the comparison.

You need
A Pagescreen account, and a SQIBS API token
Setup time
About 5 minutes
Result
Visual changes open SQIBS incidents

How it works

Pagescreen
Alert fires
A monitored page changes visually.
Pagescreen
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 monitor label.

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 Pagescreen template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event" change Opens an incident for detected changes.
Title from "label" Becomes the incident title.
Description from "compare_link" A link to the before and after comparison.
  1. Choose the Priority for these incidents and click Save.

Pagescreen also sends an event for every new capture. Those do not contain change, so they are ignored. To get them too, add a second filter for that event name. Values in Key value contains must all be present (AND). To open incidents for more than one value, add one filter per value.

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 Pagescreen

  1. In Pagescreen, open Integrations and add a webhook with your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=pagescreen&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 Add Webhook, then create a monitoring (Create Monitoring) for the pages you want to watch and turn the webhook on for it.

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. Change a test page you monitor, or wait for the next capture of a page that changes.
  2. In SQIBS, a new incident opens. The payload looks like this:
{
  "event": "change",
  "uuid": "ab996c58-31b9-4d39-a844-4c40ab473271",
  "url": "https://www.example.com",
  "label": "Home page",
  "change": 9.37,
  "view_link": "https://app.pagescreen.io/capture/view/123",
  "compare_link": "https://app.pagescreen.io/capture/compare/123"
}

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 Pagescreen 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 Pagescreen sees the home page change outside a release window, SQIBS can run a workflow that compares the deployed version with the expected one.

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: