Integrations
Edge delta
Overview
This document provides a detailed guide to integrating Edge Delta with Callgoose SQIBS for real-time Incident Management based on telemetry alert events.
The integration uses Edge Delta Webhook Output to send alert payloads into Callgoose, where API Filters automatically create and resolve incidents based on alert lifecycle.
Prerequisites
Before beginning, ensure you have:
- A Callgoose SQIBS account with permissions to create API Filters and integration endpoints
- An Edge Delta workspace with access to configure:
- Webhook Output (Destination)
- Monitors / Alert rules
- A valid Callgoose API token and Api endpoint URL.
- A test monitor in Edge Delta to validate webhook delivery and payload structure
1. Prepare Callgoose: Obtain Endpoint & Token
1.1 Retrieve Callgoose API Endpoint
In Callgoose, generate or locate your Process Endpoint:
https://****.callgoose.com/v1/process?from=EdgeDelta&token=xxxx
Store the API token securely and never commit it to source control.
2. Configure Edge Delta Webhook
Edge Delta supports webhook notifications for alert events through the Webhook Output Node.
2.1 Choose Where to Add Webhook Output
You can configure the webhook in:
- Monitor Alerting: Notifications on alert firing/recovery
- Pipeline Graph: Add node: Webhook Output / Notification
2.2 Webhook Configuration Fields
Webhook URL:Callgoose endpoint from Step 1
HTTP Method:POST
Content Type: application/json
Send Recovery / Resolved Alerts: Must be Enabled for auto-resolution in Callgoose
Suppression Window: (Optional)Enable to avoid alert flooding
Once completed: Save and enable the webhook configuration
2.3 Payload Template
Use Edge Delta templating to include alert identifiers:
{
"alert_id": "{{ .item.signal.signal_id }}",
"alert_title": "{{ .item.signal.title }}",
"description": "{{ .item.signal.description }}",
"severity": "{{ .item.signal.severity }}",
"timestamp": "{{ .item.timestamp }}"
}
You can include fields from .item.resource, .item.signal.value, etc.
3. Example Edge Delta Payloads
Alert Firing Example
{
"status": "firing",
"alert_id": "ed-alert-09922",
"alert_title": "High Error Rate",
"description": "Error% > 5% for auth-service",
"severity": "critical",
"timestamp": "2025-10-01T11:50:00Z"
}
Alert Recovery Example
{
"status": "resolved",
"alert_id": "ed-alert-09922",
"resolved_at": "2025-10-01T11:55:42Z"
}
Confirm actual payload keys in Callgoose API logs — use those exact fields while mapping API filters.
4. Create API Filters in Callgoose SQIBS
Callgoose API Filters convert incoming Edge Delta webhook alerts into incidents.
Use two filters:
- Trigger Filter (create incident)
- Resolve Filter (auto-resolve)
4.1 Trigger Filter — Create Incident
Use the following settings:
- Payload JSON Key: "status"
- Key Value Contains: firing
- Map Incident With: "alert_id"
- Incident Title: "alert_title"
- Incident Description: "description" (optional — leave empty to use full JSON)
This filter creates an incident whenever Edge Delta sends a firing alert.
4.2 Resolve Filter — Auto-Resolve Incident
Use the following settings:
- Payload JSON Key: "status"
- Key Value Contains: resolved
- Incident Mapped With: "alert_id"
This ensures the incident is resolved when the corresponding Edge Delta alert clears.
Refer to the API Filter Instructions and FAQ for more details.
5. Verify & Test the Integration
5.1 Webhook Test
Trigger a test alert condition in Edge DeltaConfirm payload visible in Callgoose API Logs
5.2 Validate Field Mapping
Match exact key names from received JSON in logs
Update filters accordingly
5.3 Functional Test
Perform the following validation steps:
- Trigger an alert in Edge Delta:An Incident should be created automatically in Callgoose
- Recover the alert in Edge Delta:The corresponding Incident should be auto-resolved in Callgoose
Ensure that both events use the same alert_id for accurate mapping
6. Troubleshooting
If issues occur during integration, check the following:
- No incoming payload received:Verify the endpoint URL, token, and that the webhook is enabled in Edge Delta
- Incidents not being created:Confirm Trigger Filter field/value mapping matches the payload (status = firing)
- Incidents not auto-resolving:Ensure Edge Delta sends recovery alerts and the payload includes "status": "resolved"
- Incorrect or missing payload fields:Check Callgoose API logs and update filter mappings using exact payload keys
- Too many incidents generated: Enable a suppression window in Edge Delta to reduce alert noise
7. Conclusion
Integrating Edge Delta with Callgoose SQIBS transforms system alert signals into actionable incidents with full lifecycle automation. Proper Trigger & Resolve filter configuration ensures operational continuity with accurate alert-to-incident transformation
