Overview

Most monitoring tools can send a webhook: an HTTPS POST when an alert fires. Point it at SQIBS and add an API filter, and the tool's alerts become incidents. Use email only for tools that cannot send webhooks.

You need
A SQIBS service and API token
Where
Your monitoring tool
Result
The tool's alerts in SQIBS

First, check the integrations list

If your tool is in the integrations, follow its guide: it has the exact steps and a ready filter.

Any tool: webhook

  1. In SQIBS, add an API filter to the service.
  2. Build your endpoint and add an API token.
  3. In your tool, find the alert channel called webhook (sometimes HTTP endpoint or custom integration), enter the URL, and choose POST.
  4. If the tool lets you write the payload, send JSON with clear keys: a status that differs between firing and resolved, an id that stays the same, and a summary for the title.
  5. Send a test with API tracking on, and refine the filter with the JSON key creator.

SQIBS accepts POST requests only.

Any tool: email

Set up an email integration, then add the service's email address as an alert recipient in your tool. Email cannot resolve incidents.

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.

Then trigger a test alert in your tool and check the API log.