Acceldata

Overview

This document provides a detailed guide to integrating Acceldata (Pulse / ADOC) with Callgoose SQIBS for real-time incident management, data-quality/observability alerting, and automated incident creation and resolution.

The integration uses Acceldata notification channels (Webhook) to send alert events to Callgoose, where API Filters convert them into incidents that are automatically created and (optionally) resolved. Acceldata supports webhook notification channels and templated notification types that can be used to generate consistent JSON payloads for external systems.

Prerequisites

• An Acceldata account with permissions to manage Alerts / Notification Channels (Pulse / Torch access).
• A Callgoose SQIBS account with permissions to create API Filters and access to create webhook/process endpoints.
• A valid Callgoose API token and Callgoose API endpoint (kept secret).
• A test Acceldata alert or rule (recommended) to validate webhook delivery and payload structure.
• Familiarity with Acceldata’s alerting UI or JSON alert templates and with Callgoose API Filters.

1. Obtain API Token and Endpoint Details

1.1 Generate an API Token

Create a Callgoose API token in your Callgoose account. Save it securely — it will be appended to the Callgoose process endpoint URL or provided as a header depending on your chosen authentication method.

1.2 Construct the Callgoose Webhook Endpoint

Construct or locate the Callgoose process endpoint that will receive Acceldata webhooks. You will use this URL in Acceldata’s webhook/notification channel configuration. Keep the token secret and never commit it to source control.

2. Configuring Acceldata to Send Alerts

Acceldata provides Notification Channels (Pulse / Torch) where you can add Webhook destinations and attach them to alerts or actions. Use a dedicated webhook channel for Callgoose so payloads are consistent.

2.1 Create a Webhook Notification Channel (Acceldata)

• In Acceldata UI, open Settings → Notification Channels (or the Pulse/Torch Actions → Notifications area).
• Click Add Notification Channel and choose Webhook as the channel type.
• Configure channel fields:
• Name: Callgoose SQIBS (or a descriptive name)
• Webhook URL: your Callgoose process endpoint (from section 1.2)
• HTTP Method: POST
• Content Type: application/json
• Headers (optional): use Authorization or an API key header if you prefer header-based auth instead of token-in-URL
• Optionally set a retry/backoff policy if the Acceldata UI provides those settings.
• Save and Test the channel using Acceldata’s test functionality (if present).

2.2 Attach the Webhook Channel to an Alert or Action

• Open your alert rule (Pulse) or action (Torch) that should notify Callgoose.
• Under Notifications (or the alert’s notification step), select the Callgoose webhook channel you created.
• Save the alert/action so future alerts will POST to Callgoose.

2.3 Configure Payload Template

Acceldata supports templated notification payloads; prefer a small, predictable JSON payload so Callgoose API Filters can map fields reliably. If Acceldata exposes variables in the UI, create a template similar to the examples below.

3. Example Acceldata Webhook Payloads

Note: inspect actual payloads sent by Acceldata (use Callgoose API logs) and adapt filters to match exact key names.

3.1 Trigger / Open Event

{
  "status": "firing",
  "alert_name": "Dataset Freshness Miss - orders.daily",
  "alert_id": "adoc-alert-2025-9876",
  "severity": "critical",
  "rule_name": "freshness_lag_rule",
  "asset": "orders.daily",
  "metric": "freshness_lag_seconds",
  "value": 86400,
  "threshold": 3600,
  "timestamp": "2025-11-24T07:30:00Z",
  "details": {
    "namespace": "analytics",
    "pipeline": "etl-order-load",
    "run_id": "run-2025-11-24-07"
  }
}

3.2 Resolved Event

{
  "status": "resolved",
  "alert_name": "Dataset Freshness Miss - orders.daily",
  "alert_id": "adoc-alert-2025-9876",
  "resolved_at": "2025-11-24T07:42:00Z"
}

4. Configuring Callgoose SQIBS

Callgoose API Filters transform incoming Acceldata webhooks into incidents. Create two filters: Trigger (create incident) and Resolve (auto-resolve).

4.1 Trigger Filter — Create Incident

• Payload JSON Key: "status"
• Key Value Contains: firing (or the exact value Acceldata sends for active alerts)
• Map Incident With: "alert_id" (ensures correlation across open/close)
• Incident Title: "alert_name"
• Incident Description: prefer "rule_name" or leave empty to store the full payload

This filter will create an incident when Acceldata raises an alert.

4.2 Resolve Filter — Auto-Resolve Incident

• Payload JSON Key: "status"
• Key Value Contains: resolved
• Incident Mapped With: "alert_id"

This ensures the incident created for alert_id is resolved when Acceldata sends a resolved event.

5. Verify and Test the Integration

5.1 Test Initial Delivery

• Use the Acceldata webhook channel Test function (or temporarily fire a test alert) to send a sample payload.
• In Callgoose, open API Request Logs and verify the webhook arrived and returned HTTP 200.

5.2 Inspect Exact Payload

• Copy the exact JSON keys from Callgoose API logs — use those exact keys in your API Filter configuration to avoid mismatches.

5.3 End-to-End Test

• Trigger a real/simulated alert in Acceldata → Confirm Callgoose creates an incident.
• Clear the alert or wait for resolution → Confirm Callgoose auto-resolves the incident using the Resolve filter.

6. Troubleshooting

• Incoming Payload Not Received
• Check Acceldata notification logs / action executions for delivery errors.
• Verify the Callgoose endpoint URL, token, and any headers.
• Ensure network egress from Acceldata (if self-hosted) to Callgoose is permitted.
• Incidents Not Created
• Verify the Trigger Filter’s JSON key and value match the live payload exactly (case sensitive).
• Check Callgoose API logs for 4xx/5xx responses and correct authentication.
• Incidents Not Auto-Resolving
• Confirm Acceldata is configured to send resolved/clear events.
• Ensure alert_id in the resolved payload exactly matches the created incident’s mapping key in Callgoose.
• Wrong or Missing Payload Fields
• Use the Callgoose API request log to inspect the full payload.
• Update the Acceldata notification template (or JSON mode) to include the required fields, then re-test.

7. Security Considerations

• Keep the Callgoose API token private and rotate tokens periodically.
• Prefer header-based authentication (Authorization: Bearer <token>) over embedding a token in the URL, if both systems support it.
• Use HTTPS endpoints only for webhook delivery.
• Limit the permissions/scope of the API token used for integrations.

8. Conclusion

By configuring an Acceldata webhook notification channel and mapping a concise, consistent JSON payload into Callgoose API Filters, teams can convert data-observability alerts into actionable incidents automatically. This setup reduces time-to-detect and time-to-remediate for data pipeline and quality issues, while keeping alerting logic maintainable and testable.

For further customization or advanced use cases, refer to the official documentation for both Acceldata and Callgoose SQIBS:

• Acceldata Documentation
• Callgoose SQIBS API Token Documentation
• Callgoose SQIBS API Endpoint Documentation
• API Filter Instructions and FAQ
• How to Send API