Embrace

Overview

This document provides a detailed guide to integrating Embrace 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 Embrace. The guide includes steps for setting up alerts in Embrace, configuring webhook notifications, creating API filters in Callgoose SQIBS, and troubleshooting.

Prerequisites

• Embrace Account: Access to Embrace 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 Embrace.

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 Embrace will be sent.

2. Debugging and Troubleshooting

You can enable debugging in the API tokens used with Embrace 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 Embrace to Send JSON Payloads

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

3.1 Integration Steps

• Log in to Embrace
• Use your credentials to log in to your Embrace account.
• Integrate Embrace SDK
• Follow Embrace’s documentation to integrate the SDK with your application.
• Access Webhooks Integration
• On the Embrace dashboard, go to Settings → Integrations → Webhooks.
• Add Webhook Details
• Provide a nickname for the webhook and paste the API endpoint URL from Callgoose SQIBS. For more details, click here
• Test Webhook Connection
• Click Test to confirm that the endpoint connection is working.
• Verify API Logs
• Check the Callgoose SQIBS API logs to ensure the connection was successful.
• Save Webhook
• Save the webhook configuration.

3.2 Alert Configuration

• Open Alerts Section
• From the Embrace dashboard, navigate to the Alerts section.
• Add a New Alert
• Click Add Alert to create a new alert.
• Configure Alert Settings
• Set up the alert conditions and thresholds according to your requirements.
• Assign Webhook
• Under the Send to Webhooks section, select the webhook created earlier.
• Save Alert
• Save the alert configuration.

3.3 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 Embrace alerts, you need to create API filters based on the JSON payloads received.

4.1.1 Example JSON Payloads from Embrace

Alert Triggered

json

{
  "msg": "",
  "version": "1.0",
  "alert": {
    "id": "8vOXjpQ",
    "name": "Callgoose Alert",
    "type": "metric",
    "metric_props": {
      "dynamic_filters": [],
      "error_level": "4.000",
      "error_recover_level": "1.000",
      "evaluation_method": "greater than or equal",
      "filters": [],
      "group_by": "",
      "metric": "Network Request",
      "min_count": null,
      "warning_level": "3.000",
      "warning_recover_level": "2.000",
      "window_function": "average",
      "window_size_in_secs": 300
    }
  },
  "app": {
    "environment": "Development",
    "id": "****",
    "name": "Test App",
    "platform": "Web"
  },
  "event": {
    "id": "vrAmRqN",
    "ts": 1756462620,
    "type": "metric",
    "metric_props": {
      "new_state": "Error",
      "old_state": "Normal",
      "value": "4.000"
    }
  },
  "links": {
    "dashboard_url": "https://dash.embrace.io/app/****/monitors/type/history/status/vrAmRqN",
    "monitor_url": "https://dash.embrace.io/app/****/monitors/type/managed/edit/8vOXjpQ"
  },
  "ts": 1756462861
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see an Embrace 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: "event"."metric_props"."new_state"
• Key Value Contains: null
• Map Incident With: null
• Incident Title From: "alert"."name"
• 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 Embrace.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Monitoring Alert:
• Trigger a condition in Embrace that causes an alert (e.g., Manually make an error in your app).
• 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.
• Embrace Permissions: Confirm that the webhook in Embrace 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 Embrace 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 Embrace matches the expected structure.

8. Conclusion

This guide provides a comprehensive overview of how to integrate Embrace with Callgoose SQIBS for effective incident management. By following the steps outlined, you can ensure that alerts from Embrace 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 Embrace and Callgoose SQIBS:

• Embrace 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 Embrace.