Integrations
Dashbird
Overview
This document explains how to integrate Dashbird with Callgoose SQIBS for real-time Incident Management, automated incident resolution, and event-driven automation.
Dashbird monitors AWS serverless environments and can send alert notifications using Webhook channels. These webhook payloads are sent to Callgoose SQIBS, where API Filters convert them into incidents that can auto-create, auto-update, and auto-resolve.
This guide covers configuration of Dashbird Webhooks, JSON payload examples, Callgoose SQIBS API filter setup, troubleshooting, and security considerations.
Prerequisites
Before starting, ensure you have:
- A Dashbird account with permissions to create Alerts and Notification Channels.
- A Callgoose SQIBS account with permissions to create API Tokens and API Filters.
- A Callgoose API Webhook Endpoint.
- A Callgoose API Token.
1. Obtain API Token and Endpoint
1.1 Generate an API Token
Create an API token in Callgoose SQIBS and store it securely.
1.2 Identify the Endpoint
Your endpoint will follow this format:
https://<org>.callgoose.com/v1/process?from=Dashbird&token=<CALLGOOSE_TOKEN>
Use from=Dashbird so incoming payloads are easily identified in logs.
2. Configure Dashbird to Send Alerts
Dashbird supports webhook-based alerting through Notification Channels. You will create a webhook channel and attach it to an Alert rule.
2.1 Create a Webhook Notification Channel
- Open Dashbird → Notification Settings
- Click Add Channel
- Select Webhook
- Configure:
- Name: Callgoose SQIBS
- Method: POST
- URL: Your Callgoose endpoint
- Content-Type: application/json
Dashbird also supports adding custom headers if needed.
2.2 Signature Header (Recommended)
Dashbird sends an x-dashbird-signature header for authenticity verification.
Callgoose can optionally validate this to ensure the payload came from Dashbird.
2.3 Attach the Webhook to a Dashbird Alert Rule
- Navigate to Alerts
- Create or edit an alert
- Under Notification Targets, select Callgoose SQIBS
- Save the alert rule
2.4 Test the Webhook
Use Dashbird’s Send Test Notification button to send a sample payload.
Verify delivery inside Callgoose → API Logs.
3. Example Dashbird JSON Payloads
Dashbird does not enforce a single fixed JSON format.
The following samples are representative only.
Always use an actual payload captured from your Dashbird test to configure filters precisely.
3.1 Triggered Alert Payload (Example)
{
"event": "ALARM_TRIGGERED",
"alert_id": "dbd-123456",
"alert_name": "High Error Rate - Orders Lambda",
"status": "alarm",
"severity": "critical",
"function_name": "orders-service-lambda",
"region": "us-east-1",
"metric": "ErrorRate",
"value": 18.5,
"threshold": 10,
"timestamp": "2025-01-25T12:30:14Z",
"dashboard_url": "https://dashbird.io/alert/dbd-123456"
}
3.2 Resolved Alert Payload (Example)
{
"event": "ALARM_RESOLVED",
"alert_id": "dbd-123456",
"alert_name": "High Error Rate - Orders Lambda",
"status": "ok",
"severity": "info",
"function_name": "orders-service-lambda",
"timestamp": "2025-01-25T12:37:14Z",
"dashboard_url": "https://dashbird.io/alert/dbd-123456"
}
4. Configure Callgoose SQIBS API Filters
Create two API Filters:
- Trigger Filter → Create incident
- Resolve Filter → Resolve incident
Use exact JSON keys from your real Dashbird payload logs.
4.1 Trigger Filter (Create Incidents)
- Payload JSON Key: status
- Key Value Contains: alarm
- Map Incident With: alert_id
- Incident Title: alert_name
- Incident Description: alert_name or leave empty to recieve full payload as description
4.1.2 Resolve Filter (Resolve Incidents)
- Payload JSON Key: status
- Key Value Contains: ok
- Incident Mapped With: alert_id
Ensure the same mapping key (alert_id) is used in both filters.
5. Testing & Validation
5.1 Trigger an Alert
- Lower alert thresholds or generate an error
- Dashbird sends an alarm payload
- Callgoose creates an incident
5.2 Resolve the Alert
- Restore normal conditions
- Dashbird sends an ok payload
- Callgoose resolves the incident
6. Debugging & Troubleshooting
Common Issues & Fixes
ProblemExplanation / FixNo incident createdTrigger filter does not match the exact Dashbird status value.Incidents not resolvingResolve filter does not match status or alert_id.Duplicate incidentsUse alert_id as unique mapping.Payload not receivedWebhook URL incorrect or endpoint unreachable.UnauthorizedToken missing or incorrect, or headers not accepted.
Check Callgoose API Logs for incoming payloads and error messages.
7. Security Considerations
- Always use HTTPS for webhook endpoints.
- Keep API tokens private and rotate periodically.
- Prefer placing tokens in headers rather than URL query parameters.
- Validate Dashbird’s x-dashbird-signature header for authenticity.
- Limit access to the ingestion endpoint using IP allowlists when possible.
8. Conclusion
By configuring Dashbird Webhook Channels and precise API Filters in Callgoose, you ensure that cloud-native issues are detected, routed, and resolved efficiently. For further customization or advanced use cases, refer to the official documentation for both Aha and Callgoose SQIBS:
