Overview
Send BlazeMeter API Monitoring results to Callgoose SQIBS. A webhook notification posts each test run to your SQIBS API endpoint. SQIBS opens an incident when a test fails and resolves it when the test passes again.
How it works
fail opens it, pass 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
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose BlazeMeter. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "result" |
fail |
Opens an incident. |
| Resolve | "result" |
pass |
Resolves the open incident. |
| Match | "test_id" |
Ties the resolve message to the incident it opened. | |
| Title from | "test_name" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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: Create an API test with a schedule
- In BlazeMeter, open API Monitoring, name the test and click Create Test.
- Set the request (method, URL, and any headers or authentication), then add Assertions for success, for example status code equals 200 and response time under 500 ms.
- On the Schedules tab, click Add Schedule and choose how often the test runs.
Step 3: Send the results to SQIBS
- In the test Editor, click the bell icon (notifications) and choose Webhooks.
- Enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=blazemeter&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.
- Save the notification. By default it sends every run; SQIBS opens incidents only for runs with
"result": "fail".
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.
- Run the test against an endpoint that fails one assertion.
- In SQIBS, a new incident opens, titled with the test name. The payload looks like this (shortened):
{
"test_name": "Checkout API",
"test_id": "180e9b3a-bff1-4c7a-9a4e-2c5b1e3d7a10",
"result": "fail",
"bucket_name": "Production",
"environment_name": "Test Settings",
"region_name": "US California",
"test_run_url": "https://www.runscope.com/radar/abc/180e9b3a/results/9f1c",
"started_at": 1764000000.99,
"finished_at": 1764000003.14
}
- Fix the endpoint and run the test again. When it passes, 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 BlazeMeter webhook.
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 API test fails because the service stopped responding, SQIBS can run a workflow that restarts the API service and reruns its health check.
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.