Flagsmith

Overview

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

Prerequisites

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

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

2. Debugging and Troubleshooting

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

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

3.1 Integration Steps

• Log in to Flagsmith
• Use your account credentials to sign in.
• Complete Initial Setup
• Finish the setup process if prompted.
• Navigate to Your Organisation
• Click on the organisation you created.
• Go to Organisation Settings.
• Access Webhooks
• In the settings menu, select Webhooks.
• Click on Create Audit Webhook.
• Configure the Webhook
• Paste the API endpoint URL provided by Callgoose SQIBS.
• For more details, visit this link: (URL Link)
• Example Payload
• When an event triggers, the webhook payload will look like this:

{
    "created_date": "2020-02-23T17:30:57.006318Z",
 "log": "New Flag / Remote Config created: my_feature",
 "author": {
  "id": 3,
  "email": "user@domain.com",
  "first_name": "Kyle",
  "last_name": "Johnson"
 },
 "environment": null,
 "project": {
  "id": 6,
  "name": "Project name",
  "organisation": 1
 },
 "related_object_id": 6,
 "related_object_type": "FEATURE"
}

• Finalize the Setup
• Click on Create Webhook.
• You will now start receiving all audit webhook alerts.

4. Configuring Callgoose SQIBS

4.1 Create API Filters in Callgoose SQIBS

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

4.1.1 Example JSON Payloads from Flagsmith

Alert Triggered

json

{
	"data": {
		"author": {
			"email": "user@domain.com",
			 "first_name": "Jane",
			 "id": 1,
			 "last_name": "Doe"
		},
		 "created_date": "2020-02-23T17:30:57.006318Z",
		 "environment": null,
		 "log": "New Flag / Remote Config created: my_feature",
		 "project": {
			"id": 1,
			 "name": "Test Project",
			 "organisation": 1
		},
		 "related_object_id": 1,
		 "related_object_type": "FEATURE"
	},
	 "event_type": "AUDIT_LOG_CREATED"
}

4.2 Configuring API Filters

4.2.1 Integration Templates

If you see an Flagsmith 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_type"
• Key Value Contains: null
• Map Incident With: null
• Incident Title From: "event_type"
• 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 Flagsmith.

5. Testing and Validation

5.1 Triggering Alerts

• Simulate a Monitoring Alert:
• Trigger a condition in Flagsmith that causes an alert (e.g., Manually crate an audit log).
• 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.
• Flagsmith Permissions: Confirm that the webhook in Flagsmith 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 Flagsmith 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 Flagsmith matches the expected structure.

8. Conclusion

This guide provides a comprehensive overview of how to integrate Flagsmith with Callgoose SQIBS for effective

incident management. By following the steps outlined, you can ensure that alerts from Flagsmith 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 Flagsmith and Callgoose SQIBS:

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