Overview

Send Plesk 360 monitoring alerts to Callgoose SQIBS. A webhook notification posts each alert to your SQIBS API endpoint. SQIBS opens an incident for a problem on a server or website and resolves it when the alert is over.

You need
A Plesk 360 account with monitoring, and a SQIBS API token
Setup time
About 10 minutes
Result
Plesk 360 alerts open and resolve SQIBS incidents

How it works

Plesk 360
Alert fires
A server or website monitor raises an alert.
Plesk 360
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
A problem state opens it, OK 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 Plesk 360 template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "event"."status" OK Resolves the open incident.
Trigger "event"."status" Opens an incident for every other status (critical, warning).
Match "event"."id" Ties the OK message to the incident it opened.
Title from "event"."description" Becomes the incident title.
Description from "event"."host" The server becomes the description.
  1. Choose the Priority for these incidents and click Save.

SQIBS checks the Resolve filter before the Trigger filter, so a Trigger with no value opens an incident for every other message (any problem state) while recoveries resolve. Nested keys are written with a quoted name for each level, like "event"."status", not event.status.

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 the webhook in Plesk 360

  1. In Plesk 360, open the monitoring notification settings and add a webhook (custom URL) notification.
  2. Set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=plesk360&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. If you can shape the message, use this structure; otherwise send one test and build the filter from the payload in the API log:
{
  "event": {
    "id": "<event id>",
    "status": "<status>",
    "severity": "<severity>",
    "description": "<description>",
    "host": "<server>"
  }
}
  1. Turn the notification on for the servers and websites you want in SQIBS.

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. Send a test notification, or make a test website unreachable.
  2. In SQIBS, a new incident opens.
  3. When the problem is over, the OK message 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 Plesk 360 notification.

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 Plesk 360 reports a website down, SQIBS can run a workflow that restarts the web server and PHP-FPM on that server.

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: