Tiger Data

Overview

This document provides a detailed guide to integrating Tiger Data with Callgoose SQIBS for real-time Incident Management, alert-based incident creation, and automated resolution.

Tiger Data currently does not provide native webhook-based alert delivery. Instead, alerts are routed through Grafana Alertmanager, and Grafana forwards alert events to Callgoose SQIBS via webhook.

The integration works as follows:

• Tiger Data is connected to Grafana as a data source.
• Tiger Data dashboards and alert rules are created inside Grafana.
• Grafana sends alert event payloads to Callgoose SQIBS using a webhook notification channel.
• Callgoose API Filters convert the incoming alert payloads into incidents and auto-resolve them.

Prerequisites

Before beginning, ensure you have the following:

• A Callgoose SQIBS account with permissions to create API Filters and access the integration endpoint.
• A Tiger Data instance with access to metrics or datasets used for alerting.
• A Grafana instance with admin-level access to configure alert rules and notification channels.
• A valid Callgoose API token and Endpoint URL.
• A test Grafana alert rule (recommended) for validating webhook delivery and payloads.

1. Prepare Callgoose: Obtain Endpoint and Token

1.1 Retrieve Callgoose API Endpoint

Generate or locate your Callgoose process endpoint:

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

Store the API token securely and never commit it to source control.

2. Configure Tiger Data with Grafana

Tiger Data does not provide standalone alerting or webhook integrations.

To enable alerting, you must first connect Tiger Data to Grafana.

2.1 Add Tiger Data as a Grafana Data Source

Inside Grafana:

• Go to Data Sources
• Click Add Data Source
• Choose Tiger Data (or relevant plugin/connector based on your deployment)
• Provide the required connection fields:
• Host
• Port
• Authentication method
• Database/workspace selection

Save and test the connection.

2.2 Create Dashboards and Alert Queries

Using the connected Tiger Data metrics:

• Create a new Grafana dashboard
• Add panels that query Tiger Data
• Convert the panel into an Alert Rule:
• Define condition
• Set threshold logic
• Select evaluation interval

3. Configure Grafana Webhook

Once alert rules are defined, configure a webhook notification channel.

3.1 Choose the Webhook Scope

Grafana supports two levels of webhook configuration:

• Global Notification Channel level
• Alerting → Notification Channels → Add Channel → Webhook
• Per Alert Rule level
• Alert Rule → Contact Points → Webhook

Grafana supports alerts from Tiger Data queries without limitations.

3.2 Configure Webhook Fields

Set the following options:

• Webhook URL:
• Callgoose endpoint from Step 1
• HTTP Method:
• POST
• Content Type:
• application/json
• Include Resolved Alerts:
• Enable this to support automatic resolution in Callgoose.

Save and enable the webhook.

3.3 Verification Headers

Grafana may include metadata headers such as:

• X-Grafana-Rule-Uid
• X-Grafana-Org-Id
• X-Prometheus-Alertmanager-Version

These are optional and do not need configuration inside Callgoose.

4. Example Grafana Payloads

Below are simplified examples of Grafana alert payloads.

4.1 Firing Payload Example

{
  "status": "firing",
  "alerts": [
    {
      "status": "firing",
      "labels": {
        "alertname": "High Query Latency",
        "service": "tigerdata",
        "severity": "critical"
      },
      "annotations": {
        "summary": "Tiger Data latency high",
        "description": "Query latency exceeded 500ms"
      },
      "startsAt": "2025-10-01T12:05:00Z"
    }
  ]
}

4.2 Resolved Payload Example

{
  "status": "resolved",
  "alerts": [
    {
      "status": "resolved",
      "labels": {
        "alertname": "High Query Latency",
        "service": "tigerdata",
        "severity": "critical"
      },
      "annotations": {
        "summary": "Latency back to normal"
      },
      "endsAt": "2025-10-01T12:15:22Z"
    }
  ]
}

Inspect your actual payloads inside Callgoose API Log and use these fields in your API Filter mappings.

5. Create API Filters in Callgoose SQIBS

Callgoose API Filters convert incoming Grafana webhook payloads into incidents.

Use two filters:

• Trigger Filter (create incident)
• Resolve Filter (auto-resolve)

5.1 Trigger Filter — Create Incident

Use the following settings:

• Payload JSON Key: status
• Key Value Contains: firing
• Map Incident With: alerts.0.labels.alertname
• Incident Title: alerts.0.annotations.summary
• Incident Description: leave empty (full JSON captured automatically)

This filter creates an incident whenever Grafana fires a new alert.

5.2 Resolve Filter — Auto-Resolve Incident

Use the following settings:

• Payload JSON Key: status
• Key Value Contains: resolved
• Incident Mapped With: alerts.0.labels.alertname

This ensures the incident is resolved when the corresponding Grafana alert clears.

6. Verify and Test the Integration

6.1 Test Initial Delivery

• Create a broad test alert rule in Grafana
• Trigger a Test Webhook
• Confirm delivery inside Callgoose API Logs

6.2 View Exact Payload

Use Callgoose’s API request logs to inspect the exact JSON payload.

Copy field names directly from these logs for accurate filter configuration.

6.3 Final Verification

• Trigger an alert in Grafana → Incident should be created
• Clear the alert → Incident should be auto-resolved
• Confirm mapping using alertname

7. Troubleshooting

• Incoming Payload Not Received
• Check Grafana webhook delivery status
• Verify the endpoint URL and token
• Ensure filters match the payload structure
• Incidents Not Auto-Resolving
• Check if Grafana sent status=resolved
• Confirm alertname matches between firing and resolved
• Ensure the “Include Resolved Alerts” option is enabled
• Wrong or Missing Payload Fields
• Inspect live payloads in Callgoose API Logs
• Update API Filters to match the structure

8. Conclusion

Integrating Tiger Data with Callgoose SQIBS via Grafana enables real-time incident creation and automatic resolution.

By connecting Tiger Data metrics through Grafana and forwarding alerts with a webhook, you gain complete operational visibility.

Properly configured Trigger and Resolve filters ensure alerts instantly become actionable incidents—while resolution occurs automatically when systems recover.

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

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