Overview
Send AppDynamics health rule violations to Callgoose SQIBS. An HTTP request template posts each event to your SQIBS API endpoint, and two actions use it: one when a violation starts and one when it ends. SQIBS opens the incident on the first and resolves it on the second.
How it works
triggered opens it, resolved 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 AppDynamics. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "event_type" |
triggered |
Opens an incident. |
| Resolve | "event_type" |
resolved |
Resolves the open incident. |
| Match | "incident_key" |
Ties the resolve message to the incident it opened. | |
| Title from | "details"."summary" |
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 the HTTP request template
- In AppDynamics, go to Alert & Respond > HTTP Request Templates and click New.
- Set Name to
CallgooseSQIBS. Add a Custom Templating Variable namedcallgoose_event_typewith the default valuetriggered. - Under Request URL, set Method to POST, URL Encoding to UTF-8, and Raw URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=appdynamics&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.
- Set Authentication to None. Under Payload, set MIME Type to
application/json, Payload Encoding to UTF-8, and paste this body:
{
"incident_key": "${latestEvent.node.name} - ${latestEvent.application.name}",
"event_type": "${callgoose_event_type}",
"description": "${latestEvent.displayName} on ${latestEvent.node.name}",
"client": "AppDynamics",
"client_url": "${controllerUrl}",
"details": {
"event_name": "${latestEvent.displayName}",
"summary": "${latestEvent.summaryMessage}",
"event_id": "${latestEvent.id}",
"event_time": "${latestEvent.eventTime}",
"event_type": "${latestEvent.eventType}",
"application_name": "${latestEvent.application.name}",
"node_name": "${latestEvent.node.name}",
"severity": "${latestEvent.severity}",
"link": "${latestEvent.deepLink}"
}
}
- Under Response Handling Criteria, add a Success Criteria with status code 200. Under Settings, tick One Request Per Event, then click Save.
- Click Test, add an event type, and click Run Test. An incident opens in SQIBS.
Step 3: Create two actions and a policy
- Go to Actions, choose the application, click Create Action and pick Make an HTTP Request.
- Name the first action
CallgooseSQIBS - Triggeredand choose theCallgooseSQIBStemplate. Keepcallgoose_event_typeastriggered. - Create a second action,
CallgooseSQIBS - Resolved, with the same template, and setcallgoose_event_typetoresolved. Without this, the end of a violation would open a second incident instead of resolving the first. - Go to Policies and create one policy for the start: on the Trigger tab, select the health rule violation started events (critical and warning); on the Actions tab, add
CallgooseSQIBS - Triggered. - Create a second policy for the end: select the health rule violation ended and canceled events, and add
CallgooseSQIBS - Resolved.
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 template test from step 2, or let a health rule violate.
- In SQIBS, a new incident opens, titled with the event summary.
- When the violation ends, the resolved action sends
"event_type": "resolved"with the sameincident_key, 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 AppDynamics template.
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 AppDynamics reports slow response times on a node, SQIBS can run a workflow that recycles the application pool on that node.
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.