Overview

Send ClouDNS monitoring alerts to Callgoose SQIBS. ClouDNS monitoring checks can email you when a check goes down. Send those emails to the SQIBS email endpoint of your service, and SQIBS opens an incident for each one.

You need
A ClouDNS account with monitoring checks, and a SQIBS service
Setup time
About 15 minutes
Result
ClouDNS DOWN alerts open SQIBS incidents

How it works

ClouDNS
Alert fires
A monitoring check goes down.
ClouDNS
Sends an email
An email notification to the SQIBS email endpoint.
SQIBS
Email filter matches
The email filter decides whether to open an incident, and the priority.
SQIBS
Incident opens
The email subject becomes the incident title.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add an email integration in SQIBS

ClouDNS cannot post JSON to an API, so use the SQIBS email integration: every alert email becomes an incident, titled with the subject.

  1. In SQIBS, open Services, choose the service, and add an Email integration.
  2. Set From email to the address ClouDNS sends alerts from (check the sender of a test notification) and verify it from the service's detail page. SQIBS only processes mail from a verified sender.
  3. Add an email filter. Leave Subject contains and Body contains empty to open an incident for every alert email, or put a word from the alert subject in Subject contains to open only for problems.
  4. Copy the service's email endpoint (under the Service tab). New or changed email integrations can take up to 10 minutes to apply.

Email incidents open only; close them in SQIBS once the alert clears.

Step 2: Add the email notification in ClouDNS

  1. In ClouDNS, open Monitoring and choose the check (or click Add New to create one: HTTP, TCP, ping and more).
  2. In the check's Notifications area, click Create new notification and choose the email type.
  3. Enter the SQIBS email endpoint from step 1 and save.

ClouDNS also offers Webhook UP event and Webhook Down event notifications, which open a URL when the status changes. They carry no alert details, and the SQIBS API accepts only POST requests with a body, so use email for ClouDNS.

Step 3: Test it

Turn on debugging for the email integration (it switches off after 48 hours), then:

  1. Make a ClouDNS alert fire, for example with a check pointed at an address that does not answer.
  2. In SQIBS, a new incident opens, titled with the email subject.

No incident? Open the email log. If the email is there, the filter or the sender did not match. If it is not there, check the address in ClouDNS.

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 ClouDNS reports a web check down, SQIBS can run a workflow that restarts the web server and rechecks the page.

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: