Cronitor

Overview

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

Prerequisites

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

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

2. Debugging and Troubleshooting

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

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

3.1 Setting Up Webhook in Cronitor

• Log in to Cronitor
• Use your Cronitor credentials to log in.
• Navigate to Settings
• From the Cronitor dashboard, go to Settings.
• Create Webhook Integration
• In Settings, select Integrations.
• Click on Create Integration.
• Select Webhooks as the integration type.
• Enter an Integration Name for easy identification.
• Set the Webhook URL
• In the Webhook URL field, paste the endpoint URL provided by Callgoose SQIBS.
• Click Create Integration.
• Configure Notification List
• Select Default as the notification list.
• Click on Save.

3.2 Setting Up Monitor in Cronitor

• Choose Monitoring Type
• Return to the Home page.
• Select the Monitoring Type (e.g., Jobs, Heartbeats, Checks).
• For demonstration purposes, we are selecting Checks.
• Configure the Check
• Provide a name for the check.
• Paste the URL of the website or endpoint you want to monitor.
• Choose the locations where the checks should run.
• Configure Request Details
• Click on Full Configuration to access detailed settings.
• Adjust the request details based on specific monitoring requirements.
• Add Assertions
• In the Assertions field, click on Add Assertion.
• Define the conditions to be met for the check. Example: Response time < 500ms.
• Configure Alert Settings
• In the Alert Settings section, choose the notification list assigned to your webhook in the Notify field.
• Click Save Monitor to finalize the setup.

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.
• Resolve the alert to ensure the resolved state payload is also correctly sent and processed.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

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

4.1.1 Example JSON Payloads from Cronitor

Alert Triggered (type: "Alert")

json

{
  "id": "YmkIm8",
  "issue": "Healthcheck Assertion Failed / MGU",
  "monitor": "MGU",
  "type": "Alert",
  "description": "Assertion: response.time < 1000 milliseconds, Actual: 1091 milliseconds\n\nRequests:\n\n9:50:42 AM UTC from Virginia, USA\nGET https://www.mgu.ac.in/home/ [200]\nAssertion: response.time < 1000 milliseconds, Actual: 1091 milliseconds\n\n\nMore details at https://cronitor.io/app/issues/****",
  "group": null,
  "rule": "request_triggered",
  "issue_url": "https://cronitor.io/app/issues/****",
  "monitor_url": "https://cronitor.io/app/monitors/YmkIm8",
  "environment": "Production"
}

Alert Resolved (type: "Recovery")

json

{
  "id": "YmkIm8",
  "issue": null,
  "monitor": "MGU",
  "type": "Recovery",
  "description": "Message: Healthcheck assertions passed on 1 attempts.\nMore details at https://cronitor.io/app/monitors/YmkIm8",
  "group": null,
  "rule": "request_triggered",
  "issue_url": null,
  "monitor_url": "https://cronitor.io/app/monitors/YmkIm8",
  "environment": "Production"
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see an Cronitor 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: "type"
• Key Value Contains: [Alert]
• Map Incident With: "id"
• This corresponds to the unique id from the Cronitor payload.
• Incident Title From: "issue"
• 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.
• Example: If you use the "description" key in the Incident Description From field, the incident description will be the value of the "description" key. In the example JSON payload provided earlier, this would result in a description like "Assertion: response.time < 1000 milliseconds, Actual: 1091 milliseconds\n\nRequests:\n\n9:50:42 AM UTC from Virginia, USA\nGET https://www.mgu.ac.in/home/ [200]\nAssertion: response.time < 1000 milliseconds, Actual: 1091 milliseconds\n\n\nMore details at https://cronitor.io/app/issues/****".
• Resolve Filter (For Resolving Incidents):
• Payload JSON Key: "type"
• Key Value Contains: [Recovery]
• Incident Mapped With: "id"
• This ensures the incident tied to the specific id is resolved when the alert status returns to normal.

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 Cronitor.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Monitoring Alert:
• Trigger a condition in Cronitor that causes an alert (e.g., when the page load time exceeds 500ms on a monitored Website).
• Verify that an incident is created in Callgoose SQIBS with the correct information.

5.2 Resolving Alerts

• Acknowledge and Resolve the Alert:
• Once the issue is resolved in Cronitor (e.g., when the page load time returns to a normal level), verify that the incident in Callgoose SQIBS is automatically marked as resolved.

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.
• Cronitor Permissions: Confirm that the webhook in Cronitor 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 Cronitor 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 Cronitor matches the expected structure.

8. Conclusion

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

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