Overview

Send Radio Mast stream alerts to Callgoose SQIBS. Radio Mast posts a webhook when a stream goes down and again when it comes back. SQIBS opens an incident for the first and resolves it on the second.

You need
A Radio Mast account with stream monitoring, and a SQIBS API token
Setup time
About 10 minutes
Result
Stream outages open and resolve SQIBS incidents

How it works

Radio Mast
Alert fires
A monitored stream goes down or goes silent.
Radio Mast
Sends a webhook
A webhook contact posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Event type down opens it, up 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. In Select Integration Template, choose Radio Mast. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "event"."type" down Opens an incident.
Resolve "event"."type" up Resolves the open incident.
Match "event"."stream"."id" Ties the resolve message to the incident it opened.
Title from "event"."stream"."name" Becomes the incident title.
Description from "summary" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template matches on "event"."stream"."id". If your alert policy only alerts when all streams of a station are down, Radio Mast sends stream as null; in that case change Map incident with (trigger and resolve) and Incident title from to "event"."station"."id" and "event"."station"."name".

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 SQIBS as an alerting contact

  1. In Radio Mast, open Alerting, click Add Contact and choose a webhook. Give it a name, for example CallgooseSQIBS.
  2. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=radiomast&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 the contact.

Step 3: Use the contact in an alert policy

  1. In Alerting, create an alert policy (or edit one) for the stations and streams you want.
  2. Add the CallgooseSQIBS contact to the policy and save it. A contact only receives alerts once it is in a policy.

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. Open the alert policy and use its test option, or stop a test stream.
  2. In SQIBS, a new incident opens, titled with the stream name. Radio Mast's payload looks like this:
{
  "timestamp": 1764152021,
  "summary": "Example FM Alert: Stream 1 is down",
  "event": {
    "type": "down",
    "stream": {
      "id": "6ffd5f90-64dd-421d-b48a-349eee8ca535",
      "name": "Stream 1",
      "listening_url": "https://stream.example.com/mount",
      "silence": true
    },
    "station": {
      "id": "fd75e020-9569-4e9a-af3f-a8e1ea9c87d3",
      "name": "Example FM"
    }
  }
}
  1. When the stream is back, Radio Mast sends "type": "up" for the same stream, 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 Radio Mast contact.

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 Radio Mast reports a stream down, SQIBS can run a workflow that restarts the encoder service and checks the mount point 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: