Overview
Send Meegle work items to Callgoose SQIBS. A Meegle automation rule can send an HTTP request when a work item is created or changes; point it at your SQIBS API endpoint and SQIBS opens an incident, for example for every urgent bug.
How it works
Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- Add a filter with these values (there is no built-in Meegle template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "priority" |
urgent |
Opens an incident for urgent work items. |
| Match | "item_id" |
One incident per work item. | |
| Title from | "name" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
These keys come from the request body you define in step 2. If you send Meegle's default body instead, build the filter from the first message with the JSON key creator.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 automation rule in Meegle
- In Meegle, open the Space, go to Space Configuration > Automations and click New Rules.
- Choose the trigger, for example work item created for the bug type, with a condition on priority.
- Add an operation node of the type that sends an HTTP request (webhook). Set the method to POST and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=meegle&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.
- If you can define the body, send short keys such as
item_id,name,priorityand a link, filled from the work item fields. - Save and turn on the rule.
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.
- Create a test work item that meets the rule's condition.
- In SQIBS, a new incident opens. Check its keys in the JSON key creator.
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 Meegle rule.
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 urgent bug reports a failing service, SQIBS can run a workflow that checks the service health and attaches the result to the incident.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.