Bamboo

Overview

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

Prerequisites

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

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

2. Debugging and Troubleshooting

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

To configure Bamboo 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 Bamboo to ensure that the JSON payloads match those expected by Callgoose SQIBS.

3.1 Setting Up Alerts in Bamboo

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

• Log in to the Bamboo Console:
• Access the Bamboo platform using your account credentials.
• Navigate to the Notifications Section:
• In the Bamboo console, go to Administration > Notifications.
• Create a New Notification:
• Click on Add Notification to create a new notification.
• Specify Notification Conditions: Define the conditions that will trigger the notification, such as build failures, deployment issues, or custom metrics.
• Configure the Notification Method:
• Choose Webhook as the notification method to send data to a webhook.
• Webhook URL: Enter the webhook URL provided by Callgoose SQIBS.

3.2 Configuring the Webhook Notification

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

• Add Webhook URL:
• In the Webhook URL field, enter the endpoint provided by Callgoose SQIBS.
• Ensure the protocol is HTTPS for secure data transmission.
• Customize Payload Format:
• Ensure that the payload includes key fields like "status", "event", "severity", "description", "timestamp", and others as shown in the example payloads.
• Example Payload Setup:

json

{
  "build": {
    "id": "$BUILD_ID",
    "status": "$STATUS",
    "result": "$RESULT",
    "description": "$DESCRIPTION",
    "project": "$PROJECT_NAME",
    "timestamp": "$TIMESTAMP"
  }
}

• Placeholder Explanation:
• $STATUS: Replaces with the status of the build (e.g., SUCCESS, FAILURE).
• $BUILD_ID: A unique identifier for the build.
• $RESULT: The result of the build.
• $DESCRIPTION: A descriptive message of the build event.
• $PROJECT_NAME: The name of the project associated with the build.
• $TIMESTAMP: The time the build event occurred.
• 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.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

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

4.1.1 Example JSON Payloads from Bamboo

Build Failure (status: "FAILURE")

json

{
  "build": {
    "id": "build123",
    "status": "FAILURE",
    "result": "failed",
    "description": "Unit tests failed.",
    "project": "MyApp",
    "timestamp": "2024-08-05T12:00:00.000Z"
  }
}

Build Success (status: "SUCCESS")

json

{
  "build": {
    "id": "build123",
    "status": "SUCCESS",
    "result": "passed",
    "description": "Build completed successfully.",
    "project": "MyApp",
    "timestamp": "2024-08-05T12:30:00.000Z"
  }
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see a Bamboo 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: [FAILURE, ERROR]
• Map Incident With: build.id
• This corresponds to the unique build.id from the Bamboo payload.
• Incident Title From: build.description
• This will use the build description 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 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 "Unit tests failed."
• Resolve Filter (For Resolving Incidents):
• Payload JSON Key: status
• Key Value Contains: [SUCCESS]
• Incident Mapped With: build.id
• This ensures the incident tied to the specific build.id is resolved when the build status returns to success.

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 Bamboo.
• Test the Integration:
• Manually trigger a build failure in Bamboo to test if incidents are created in Callgoose SQIBS.
• Verify that the incident appears in Callgoose SQIBS with the correct title, description, and mapped values.
• Resolve the build issue in Bamboo and ensure that the corresponding incident in Callgoose SQIBS is marked as resolved.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Build Failure:
• Intentionally cause a build failure in Bamboo to trigger an alert.
• Verify that an incident is created in Callgoose SQIBS with the correct information.

5.2 Resolving Alerts

• Resolve the Build Issue:
• Once the build issue is resolved in Bamboo (e.g., the build succeeds), 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.
• Bamboo Permissions: Confirm that the webhook in Bamboo has appropriate permissions to send alerts and data to Callgoose SQIBS.
• Data Encryption: Ensure that the transmission of data between Bamboo 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 Bamboo 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 Bamboo matches the expected structure.

8. Conclusion

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

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