Overview

Send Oracle Cloud Infrastructure (OCI) Monitoring alarms to Callgoose SQIBS. Alarms publish to a Notifications topic; a small OCI Function subscribed to the topic forwards each message to your SQIBS API endpoint. SQIBS opens an incident when an alarm fires and resolves it when the alarm returns to OK.

You need
An OCI tenancy with permission to manage Monitoring, Notifications and Functions, and a SQIBS API token
Setup time
About 30 minutes
Result
OCI alarms open and resolve SQIBS incidents

How it works

OCI
Alert fires
A Monitoring alarm changes state.
OCI
Sends a webhook
The topic triggers a function, which posts to SQIBS.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
OK_TO_FIRING opens it, FIRING_TO_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 Oracle Cloud Infrastructure template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "type" FIRING_TO_OK Resolves the open incident.
Trigger "type" OK_TO_FIRING Opens an incident.
Match "dedupeKey" The alarm's unique ID: ties OK to its firing message.
Title from "title" Becomes the incident title.
Description from "body" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

OCI also sends REPEAT (still firing) and RESET (alarm reset). Neither matches these filters, so they are ignored; add a Resolve filter for RESET if you want a reset alarm to close its incident.

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.

Why a function

An OCI HTTPS (Custom URL) subscription allows only Basic authentication: no query parameters and no custom headers. SQIBS takes the API token as a Bearer header or a token parameter, so a topic cannot post to SQIBS directly. A function subscription adds the token and forwards the message unchanged.

Step 2: Create the forwarding function

  1. In OCI, create a Functions application (in a subnet with internet access) and a Python function from this code:
import io
import json
import urllib.request

from fdk import response


def handler(ctx, data: io.BytesIO = None):
    cfg = ctx.Config()  # SQIBS_URL and SQIBS_TOKEN, set in the function's configuration
    req = urllib.request.Request(
        cfg["SQIBS_URL"], data=data.getvalue(), method="POST",
        headers={"Content-Type": "application/json", "Authorization": "Bearer " + cfg["SQIBS_TOKEN"]})
    with urllib.request.urlopen(req, timeout=10) as r:
        return response.Response(ctx, response_data=json.dumps({"sqibs": r.status}),
                                 headers={"Content-Type": "application/json"})
  1. In the function's Configuration, add SQIBS_URL with your endpoint and SQIBS_TOKEN with your API token:
https://<your-endpoint>/sqibs-api/v1/process?from=oci

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

For production, keep the token in OCI Vault and read it in the function instead of storing it in the configuration.

Step 3: Connect the alarms

  1. In Notifications, create a topic, for example callgoose-sqibs, and add a subscription with protocol Function that points at the function.
  2. In Monitoring > Alarm definitions, create or edit an alarm and choose the topic as its destination. Keep the message format Raw (JSON) so the keys in step 1 match.

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. In the alarm, lower the threshold so it fires.
  2. In SQIBS, a new incident opens. The alarm message looks like this (shortened):
{
  "dedupeKey": "exampleuniqueID",
  "title": "High CPU Utilization",
  "body": "Follow runbook at https://wiki.example.com/cpu",
  "type": "OK_TO_FIRING",
  "severity": "CRITICAL",
  "timestamp": "2026-11-22T15:34:23.852Z"
}
  1. Restore the threshold. OCI sends FIRING_TO_OK with the same dedupeKey, 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 function's configuration.

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 an OCI alarm reports high CPU on a compute instance, SQIBS can run a workflow that restarts the busy service or scales the instance pool.

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: