Hyperping

Overview

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

Prerequisites

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

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

2. Debugging and Troubleshooting

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

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

3.1 Setting Up Monitor in Hyperping

• Log in to Hyperping:
• Use your credentials to access your Hyperping account.
• Create a New Monitor:
• Go to the Monitor section.
• Click on New Monitor to set up monitoring for a website.
• Configure the website details, such as:
• Name and URL
• Advanced settings like ping location, check interval, etc.
• Once configured, click on Create Monitor.

3.2 Setting Up Webhook in Hyperping

• Set Up Webhook Integration:
• Navigate to the Integrations section in Hyperping.
• Select Webhook and type a name for the integration.
• In the Webhook Endpoint field, paste the endpoint URL provided by Callgoose SQIBS. Note that the final API endpoint may vary based on authentication requirements and other URL parameters.
• Find the API endpoint details here.
• Click on Create to finalize the integration.

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

4.1.1 Example JSON Payloads from Hyperping

Alert Triggered (down: "true")

json

{
  "event": "check.down",
  "text": "[DOWN] Outage HTTPBIN for has started.",
  "check": {
    "url": "https://httpbin.org/status/400",
    "status": 400,
    "down": true,
    "date": 1731056839411,
    "downtime": 0,
    "monitorUuid": "mon_jYXcRmK6KCEvDf"
  },
  "pings": [
    {
      "original": true,
      "location": "singapore",
      "status": 400,
      "statusMessage": "BAD REQUEST"
    },
    {
      "original": false,
      "location": "mumbai",
      "status": 400,
      "statusMessage": "BAD REQUEST"
    },
    {
      "original": false,
      "location": "tokyo",
      "status": 400,
      "statusMessage": "BAD REQUEST"
    },
    {
      "original": false,
      "location": "frankfurt",
      "status": 400,
      "statusMessage": "BAD REQUEST"
    }
  ]
}

Alert Resolved (down: "false")

json

{
  "event": "check.up",
  "text": "[UP] HTTPBIN has recovered.",
  "check": {
    "url": "https://httpbin.org/status/200",
    "status": 200,
    "down": false,
    "date": 1731056918941,
    "downtime": 79,
    "monitorUuid": "mon_jYXcRmK6KCEvDf"
  }
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see an Hyperping 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: "check"."down"
• Key Value Contains: [true]
• Map Incident With: "check"."monitorUuid"
• This corresponds to the unique monitor uid from the Hyperping payload.
• Incident Title From: "event"
• 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 "text" key in the Incident Description From field, the incident description will be the value of the "text" key. In the example JSON payload provided earlier, this would result in a description like "[DOWN] Outage HTTPBIN for has started.".
• Resolve Filter (For Resolving Incidents):
• Payload JSON Key: "check"."down"
• Key Value Contains: [false]
• Incident Mapped With: "check"."monitorUuid"
• This ensures the incident tied to the specific monitorUuid 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 Hyperping.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Monitoring Alert:
• Trigger a condition in Hyperping that causes an alert (e.g., Manually bring a server down.).
• 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 Hyperping (e.g., Restore the server to normal operation.), 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.
• Hyperping Permissions: Confirm that the webhook in Hyperping 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 Hyperping 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 Hyperping matches the expected structure.

8. Conclusion

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

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