Groundcover

overview

This document provides a detailed guide to integrating Groundcover with Callgoose SQIBS for real-time incident creation, enrichment using Kubernetes intelligence, and automated incident resolution.

The integration uses Groundcover Alert Webhooks to transmit alert lifecycle events into Callgoose. Callgoose converts these payloads into incidents using configurable API Filters.

This ensures every operational alert in Groundcover becomes an actionable incident inside Callgoose sqibs.

Prerequisites

Before starting, confirm you have:

• A Callgoose SQIBS account with permissions to create API Filters and access the integration endpoint.
• A Groundcover workspace with Admin privileges for Alert Rules and Integrations
• A valid Callgoose API token and Api endpoint URL.
• At least one Groundcover alert rule ready for testing

1.Prepare Callgoose:Obtain Endpoint and Token

1.1 Retrieve Callgoose API Endpoint

Use the Callgoose process endpoint with token authentication:

https://****.callgoose.com/v1/process?from=Groundcover&token=xxxx

Keep the API token private and never store it in exposed configuration sources.

2. Configure Groundcover Webhook

2.1 Add Webhook to an Alert Rule

In Groundcover UI:

• Alerts → Select Alert → Edit Configuration → Add Notifier → Webhook

Groundcover allows alerting based on:

• Kubernetes health signals
• Network and application performance metrics
• Tracing and anomalyoverview detections

You may configure a global webhook using:

Integrations → Webhooks → Add Integration

2.2 Configure Request Options

• Webhook URL: In the URL field, paste the Endpoint URL provided by Callgoose SQIBS. The final format of the URL should be determined by referring to the Callgoose Sqibs API Endpoint Documentation.
• HTTP Method: POST
• Content-Type: application/json
• Trigger: Alert Fired&Alert Resolved Events

Enable sending resolved alerts so Callgoose can auto-resolve incidents.

2.3 Optional Security

Groundcover supports:

• Signature verification for payload integrity
• Alert source details via metadata headers

If using middleware, validate before forwarding to Callgoose.

3. Example Groundcover Webhook Payload

Actual payloads may vary depending on alert fields and rule design. Below are baseline samples for filter configuration.

Alert Fired Example

{
  "status": "firing",
  "alert_id": "gc-k8s-99281",
  "alert_name": "CrashLoopBackOff",
  "severity": "critical",
  "started_at": "2025-10-05T07:20:00Z",
  "kubernetes": {
    "namespace": "default",
    "pod": "payment-api-76844b5d8f",
    "restart_count": 5
  }
}

Alert Resolved Example

{
  "status": "resolved",
  "alert_id": "gc-k8s-99281",
  "alert_name": "CrashLoopBackOff",
  "resolved_at": "2025-10-05T07:28:14Z"
}

Confirm exact key names via Callgoose API logs and copy directly.

4. Create API Filters in Callgoose SQIBS

Callgoose API Filters convert incoming groundcover webhooks 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_name"
• Incident Description: "kubernetes" (optional — leave empty to use full JSON)

This ensures incidents are created when groundcover alerts fire.

4.2 Resolve Filter — Auto-Resolve Incident

Use the following settings:

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

The same alert_id ensures perfect linking for automated resolution.

Refer to the API Filter Instructions and FAQ for more details.

5. Verify and Test Integration

5.1 Validate Webhook Delivery

• Send a test notification from Groundcover Alert UI
• Confirm reception in Callgoose → API Request Logs

5.2 Confirm Field Mappings

• Copy exact field names from logs into API Filters
• Ensure Alert Fired + Resolved both deliver payload

6. Troubleshooting

incoming Payload Not Received: Check webhook URL, API token, groundcover integration logs

Incident does not resolve:Confirm Groundcover sends resolved state and alert_id is identical

Field mismatches:Update API Filter with real payload structure

Security signature errors:Disable or correctly validate HMAC signature

7. Conclusion

Integrating Groundcover with Callgoose SQIBS enables:

• Real-time alert-to-incident creation
• Automated resolution tracking
• Faster acknowledgment and remediation
• Smoother SRE workflows with actionable observability insights

By configuring groundcover Webhooks and mapping them through Callgoose API Filters, your alert stream becomes a synchronized incident management pipeline.

For further customization or advanced use cases, refer to:

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