Overview
Send Treo site speed alerts to Callgoose SQIBS. Treo has no generic webhook, but its Slack alert type posts a Slack-style JSON message to any URL you give it, so you point it at your SQIBS API endpoint. SQIBS opens an incident each time an alert fires.
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 Treo template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "attachments".[0]."text" |
Opens an incident for each alert message. | |
| Title from | "attachments".[0]."title" |
The page name becomes the incident title. | |
| Description from | "attachments".[0]."text" |
The alert text, for example the score that dropped. |
- Choose the Priority for these incidents and click Save.
Treo does not send a message when the metric recovers, so close these incidents in SQIBS once the page is fast again.
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 alert in Treo
- In Treo, open Pages and add the page you want to watch (New Page), if it is not there yet.
- Open Alerts and click New Alert. Choose the Slack alert type.
- In the Slack webhook URL field, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=treo&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.
- Choose the page and the condition (for example, performance score lower than 60 over 8 hours), then click Create.
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.
- Set a condition the page already fails, for a test, and wait for Treo's next check.
- In SQIBS, a new incident opens. Treo's payload looks like this:
{
"username": "Treo Alerts",
"attachments": [
{
"fallback": "Performance score is lower than 60 in the past 8 hours",
"color": "#E12D39",
"title": "Shop home page",
"title_link": "https://treo.sh/a/123/pages/2?interval=3days",
"text": "Performance score is lower than 60 in the past 8 hours"
}
]
}
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 Treo alert.
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 Treo reports the home page getting slow, SQIBS can run a workflow that purges the CDN cache and warms the page again.
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.