Sensu

Overview

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

Prerequisites

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

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.

1. Generate an API Token:

• Follow the guide on How to Create API Token in Callgoose SQIBS.

1. Find the API Endpoint:

• Refer to the Callgoose SQIBS API Endpoint Documentation to get the endpoint details where the JSON payloads from Sensu will be sent.

2. Debugging and Troubleshooting

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

To configure Sensu to generate the JSON payloads similar to the examples provided, follow the steps outlined below. These steps will guide you through setting up the necessary alerts and webhook notifications within Sensu to ensure that the JSON payloads match those expected by Callgoose SQIBS.

3.1 Setting Up Alerts in Sensu

To generate the required JSON payloads, you first need to set up alerts within Sensu.

1. Log in to the Sensu Console:

• Access the Sensu platform using your account credentials.

1. Navigate to the Monitoring Section:

• Go to the monitoring section in Sensu where you can manage checks and alerts.

1. Create a New Check:

• Create a new check that will monitor a specific metric or condition (e.g., CPU usage, memory, or disk space).
• Specify the conditions that will trigger an alert, such as a threshold being exceeded.

1. Configure the Notification Method:

• In the check configuration, set the handler to a webhook.
• Enter the webhook URL provided by Callgoose SQIBS to send the alert data.

3.2 Configuring the Webhook Notification

To ensure that the JSON payload sent matches the examples provided, follow these steps when configuring the webhook:

1. Add Webhook URL:

• In the webhook configuration, enter the URL provided by Callgoose SQIBS.

1. Customize Payload Format:

• Ensure that the payload includes key fields like "status", "check", "output", "entity", and others as shown in the example payloads.
• Example Payload Setup:

json

{
  "check": {
    "name": "check_cpu",
    "status": 2,
    "output": "CRITICAL: CPU usage is above 90%",
    "entity": "server1.sensu.io",
    "timestamp": 1672531199
  }
}

• Placeholder Explanation:
• "status": Represents the status of the check (e.g., 0 for OK, 1 for WARNING, 2 for CRITICAL).
• "name": The name of the check that triggered the alert.
• "output": The output message from the check.
• "entity": The name of the monitored entity.
• "timestamp": The time when the check was performed.

1. Test the Webhook Configuration:

• Before activating the webhook, perform a test to ensure that the JSON payload is correctly formatted and is being sent to the Callgoose SQIBS API endpoint as expected.
• Review the payload in Callgoose SQIBS to confirm that it matches the expected structure.

3.3 Finalizing and Testing

1. Save and Activate the Check:

• Once the check and webhook are correctly configured, save the configuration and activate it.

1. Validate the Integration:

• Trigger the check manually if possible to verify that the correct JSON payload is sent to Callgoose SQIBS.
• Resolve the check condition to ensure the resolved state payload is also correctly sent and processed.

1. Additional Considerations:

• Permissions: Ensure that the webhook has the necessary permissions to send alerts to the Callgoose SQIBS API endpoint.
• Security: Implement security measures such as HTTPS and API tokens to protect the data being transmitted between Sensu and Callgoose SQIBS.
• Logging and Debugging: Use the debugging and logging features in Callgoose SQIBS to monitor incoming payloads and troubleshoot any issues with the integration.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

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

4.1.1 Example JSON Payloads from Sensu

Alert Triggered (status: 2 - CRITICAL)

json

{
  "check": {
    "name": "check_cpu",
    "status": 2,
    "output": "CRITICAL: CPU usage is above 90%",
    "entity": "server1.sensu.io",
    "timestamp": 1672531199
  }
}

Alert Resolved (status: 0 - OK)

json

{
  "check": {
    "name": "check_cpu",
    "status": 0,
    "output": "OK: CPU usage is back to normal",
    "entity": "server1.sensu.io",
    "timestamp": 1672531399
  }
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see a Sensu 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: "status"
• Key Value Contains: [2, 1]
• Map Incident With: "check.entity"
• This corresponds to the unique entity name from the Sensu payload.
• Incident Title From: "check.output"
• This will use the check output message as the incident title in Callgoose SQIBS.
• 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 "output" key in the Incident Description From field, the incident description will be the value of the "output" key. In the example JSON payload provided earlier, this would result in a description like "CRITICAL: CPU usage is above 90%".
• Resolve Filter (For Resolving Incidents):
• Payload JSON Key: "status"
• Key Value Contains: [0]
• Incident Mapped With: "check.entity"
• This ensures the incident tied to the specific entity is resolved when the alert status returns to normal.

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

5. Testing and Validation

5.1 Triggering Alerts

1. Simulate a Monitoring Alert:

• Trigger a condition in Sensu that causes an alert (e.g., CPU usage exceeding a critical threshold on a monitored server).
• Verify that an incident is created in Callgoose SQIBS with the correct information.

5.2 Resolving Alerts

1. Acknowledge and Resolve the Alert:

• Once the issue is resolved in Sensu (e.g., CPU usage 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.
• Sensu Permissions: Confirm that the webhook in Sensu has appropriate permissions to send alerts and data to Callgoose SQIBS.
• Data Encryption: Ensure that the transmission of data between Sensu and Callgoose SQIBS is encrypted, especially if sensitive information is involved.

7. Troubleshooting

• No Incident Created: If no incident is created, verify that the webhook URL in Sensu 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 Sensu matches the expected structure.

8. Conclusion

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

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