Avo

Overview

This document provides a detailed guide to integrating Avo with Callgoose SQIBS for real-time Incident Management, Incident Auto Remediation, Event-Driven Automation, and other automation purposes. The integration enables automatic creation, updating, and resolution of incidents in Callgoose SQIBS based on alerts triggered in Avo. The guide includes steps for setting up alerts in Avo, configuring webhook notifications, creating API filters in Callgoose SQIBS, and troubleshooting.

Prerequisites

• Avo Account: Access to Avo for creating alerts and managing notifications.
• Callgoose SQIBS Account: With valid privileges to set up API filters and receive notifications.
• Webhook/API Endpoint: Available in Callgoose SQIBS to receive alerts from Avo.

1. Obtain API Token and Endpoint Details

To integrate with Callgoose SQIBS, you first need to obtain an API token and find the API endpoint details.

• Generate an API Token:
• Follow the guide on How to Create API Token in Callgoose SQIBS.
• Find the API Endpoint:
• Refer to the Callgoose SQIBS API Endpoint Documentation to get the endpoint details where the JSON payloads from Avo will be sent.

2. Debugging and Troubleshooting

You can enable debugging in the API tokens used with Avo notifications for troubleshooting purposes.

• Enable Debugging:
• You can update the debug value when adding or updating an API token.
• When API tracking is enabled, logs are stored in the API log section for your review. The debugging option will automatically disable after 48 hours.
• When API tracking is turned off, no logs are saved in the API log.
• Using API Log for Troubleshooting:
• The API log provides detailed information on all API calls made to Callgoose SQIBS.
• You can check the JSON values in each API log entry for troubleshooting purposes.
• Use the information in the API log to create or refine API filters to ensure incidents are created correctly based on the API payloads received.
• Callgoose SQIBS creates incidents according to your API filter configuration, giving you full control over how alerts from different services trigger incidents and alerts for your support team or automation processes.

3. Configuring Avo to Send JSON Payloads

Follow these steps to set up monitoring, alerts, and webhook integrations in Avo, ensuring that the JSON payloads generated match the required format for Callgoose SQIBS.

3.1 Setting Up Webhook Notification in Avo

• Login to Avo
• Go to the Avo platform and log in using your credentials.
• Set Up Your Account
• If you are new to Avo, follow the on-screen instructions to complete your account setup.
• Configure Webhook Notification
• In the Avo dashboard, navigate to the Publishing section.
• Set Up Integration
• Click on Set Up Integration.
• From the list of options, select Webhook.
• Click on Create Integration.
• Define Webhook Settings
• Provide a name for the webhook to identify this integration.
• Paste the endpoint URL provided by Callgoose SQIBS.
• Note: The final API endpoint may vary based on authentication and other URL parameters. Refer to the Callgoose API Endpoint Documentation to determine your final API endpoint.
• Publish
• After configuring the webhook, click on Publish to activate the integration.

3.2 Finalizing and Testing

• Validate the Integration:
• Trigger the alert condition manually if possible to verify that the correct JSON payload is sent to Callgoose SQIBS.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

To correctly map incidents from the Avo alerts, you need to create API filters based on the JSON payloads received.

4.1.1 Example JSON Payloads from Avo

Alert Triggered (type: "Alert")

json

{
"context": {
"publishInfo": {
"branchId": "master",
"branchName": "main",
"integrationId": "QdJytW4_A",
"integrationName": "Webhook",
"publishDate": "Sat, 14 Dec 2024 10:29:09 GMT",
"publishMethod": {
"type": "BranchMerge"
},
"lastUpdateId": "qxwfGpo7ZI63IITfzhAX",
"lastUpdateTimestamp": "Sat, 14 Dec 2024 10:29:08 GMT"
}
},
"eventSchemas": [
{
"meta": {
"hidden": false,
"customData": {},
"schemaType": "event"
},
"data": {
"self": {
"vendor": "app.avo",
"name": "new_event",
"format": "jsonschema",
"version": "ENTER THE VERSION"
},
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
"description": "Test Description",
"properties": {},
"additionalProperties": false,
"type": "object"
}
},
{
"meta": {
"hidden": false,
"customData": {},
"schemaType": "event"
},
"data": {
"self": {
"vendor": "app.avo",
"name": "second_event",
"format": "jsonschema",
"version": "ENTER THE VERSION"
},
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
"description": "Test Description",
"properties": {},
"additionalProperties": false,
"type": "object"
}
}
],
"contextSchemas": []
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see an Avo integration template in the "Select Integration Template" dropdown in the API filter settings, you can use it to automatically add the necessary Trigger and Resolve filters along with other values. The values added by the template can be modified to customize the integration according to your requirements.

4.2.2 Manually Add/Edit the Filter

• Trigger Filter (For Creating Incidents):
• Payload JSON Key: "context"."publishInfo"."publishMethod"."type"
• Key Value Contains: [BranchMerge]
• Map Incident With: null
• Incident Title From: "context"."publishInfo"."publishMethod"."type"
• Incident Description From: Leave this empty unless you want to use a specific key-value from the JSON payload. If a key is entered, only the value for that key will be used as the Incident Description instead of the full JSON. By default, the Incident Description will include the full JSON values.
• Resolve Filter (For Resolving Incidents):
• Payload JSON Key: null
• Key Value Contains: null
• Incident Mapped With: null

Refer to the API Filter Instructions and FAQ for more details.

4.3 Finalizing Setup

• Save the API Filters:
• Ensure that the filters are correctly configured and saved in Callgoose SQIBS.
• Double-check that all key mappings, incident titles, and descriptions are correctly aligned with the payload structure sent by Avo.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Monitoring Alert:
• Trigger a condition in Avo that causes an alert (e.g., Merge two branches).
• Verify that an incident is created in Callgoose SQIBS with the correct information.

6. Security Considerations

• API Security: Ensure that the Callgoose SQIBS API endpoint is correctly configured and that the API token is securely stored and used.
• Avo Permissions: Confirm that the webhook in Avo has appropriate permissions to send alerts and data to Callgoose SQIBS.

7. Troubleshooting

• No Incident Created: If no incident is created, verify that the webhook URL in Avo is correct and that the JSON payload structure matches the API filters configured in Callgoose SQIBS.
• Incident Not Resolved: Ensure that the resolve filter in Callgoose SQIBS is correctly configured and that the JSON payload sent by Avo matches the expected structure.

8. Conclusion

This guide provides a comprehensive overview of how to integrate Avo with Callgoose SQIBS for effective incident management. By following the steps outlined, you can ensure that alerts from Avo are automatically reflected as incidents in Callgoose SQIBS, with proper resolution tracking when the issues are resolved.

For further customization or advanced use cases, refer to the official documentation for both Avo and Callgoose SQIBS:

• Avo Documentation
• Callgoose SQIBS API Token Documentation
• Callgoose SQIBS API Endpoint Documentation
• API Filter Instructions and FAQ
• How to Send API

This documentation will guide you through the integration process, ensuring that your incidents are managed effectively within Callgoose SQIBS based on real-time alerts from Avo.