Integrations
InfluxDB
Overview
This document provides a detailed guide to integrating InfluxDB with Callgoose SQIBS for real-time Incident Management, metric-based alerting, and automated incident resolution.
The integration uses InfluxDB Webhook Notification Endpoints to send alert event payloads directly to Callgoose, where API Filters convert them into incidents that are automatically created and resolved.
Prerequisites
Before beginning, ensure you have the following:
- A Callgoose SQIBS account with permissions to create API Filters and access the integration endpoint.
- An InfluxDB 2.x instance (Cloud or OSS) with access to:
- Checks
- Notification Endpoints
- Notification Rules
- A valid Callgoose API token and API endpoint URL.
- A test InfluxDB 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=InfluxDB&token=xxxx
Store the API token securely and never commit it to source control.
2. Install InfluxDB
InfluxDB can be installed on Ubuntu, Debian, RHEL-based systems, or via Docker.
2.1 Install on Ubuntu/Debian
sudo apt update curl -s https://repos.influxdata.com/influxdata-archive.key | sudo apt-key add - echo "deb https://repos.influxdata.com/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/influxdb.list sudo apt update sudo apt install influxdb2 sudo systemctl enable influxdb sudo systemctl start influxdb
2.2 Install on RHEL / CentOS / Rocky / AlmaLinux
sudo tee /etc/yum.repos.d/influxdb.repo <<EOF [influxdb] name=InfluxDB Repository baseurl=https://repos.influxdata.com/rhel/7/x86_64/stable/ enabled=1 gpgcheck=1 gpgkey=https://repos.influxdata.com/influxdata-archive.key EOF sudo yum install influxdb2 sudo systemctl enable influxdb sudo systemctl start influxdb
2.3 Install Using Docker
docker run -p 8086:8086 \ -v $PWD/data:/var/lib/influxdb2 \ -v $PWD/config:/etc/influxdb2 \ influxdb:2
2.4 Verify Installation
Visit:
http://localhost:8086
Complete onboarding (organization, bucket, admin credentials).
3. Configure InfluxDB Webhook
InfluxDB supports webhook delivery through Notification Endpoints and Notification Rules.
3.1 Create a Webhook Notification Endpoint
- Navigate to Alerts → Notification Endpoints
- Click Create Notification Endpoint
- Select Webhook
- Configure:
- Name: Callgoose SQIBS
- Method: POST
- URL: Your Callgoose endpoint
- Content-Type: application/json
- Save the endpoint.
3.2 Create a Notification Rule
- Navigate to Alerts → Notification Rules
- Click Create Notification Rule
- Set:
- Endpoint: Callgoose SQIBS
- Status: Trigger + Recover
- Attach the rule to your InfluxDB checks.
- Save the rule.
4. Example InfluxDB Payloads
4.1 Trigger Event
{
"status": "firing",
"checkID": "cpu-check-001",
"checkName": "CPU Usage Critical",
"level": "crit",
"message": "CPU usage exceeded threshold",
"time": "2025-11-12T14:25:00Z",
"tags": {
"host": "app-server-01"
}
}
4.2 Resolve Event
{
"status": "resolved",
"checkID": "cpu-check-001",
"checkName": "CPU Usage Critical",
"time": "2025-11-12T14:30:45Z"
}
5. Create API Filters in Callgoose SQIBS
Callgoose API Filters convert incoming InfluxDB webhook events into incidents.
Use two filters:
Trigger Filter (create incident)
Resolve Filter (auto-resolve)
5.1 Trigger Filter — Create Incident
- Payload JSON Key: "status"
- Key Value Contains: firing
- Map Incident With: "checkID"
- Incident Title: "checkName"
- Incident Description:" message" (optional — or leave empty to use full JSON)
5.2 Resolve Filter — Auto-Resolve Incident
- Payload JSON Key: "status"
- Key Value Contains: resolved
- Incident Mapped With: "checkID"
6. Verify and Test the Integration
6.1 Test Initial Delivery
- Trigger a test alert using InfluxDB Checks.
- Confirm the payload appears in Callgoose API Logs.
6.2 View Exact Payload
- Inspect logs in Callgoose to confirm actual JSON fields.
- Adjust filter mapping if needed.
6.3 Final Verification
- Trigger alert condition → Incident should be created.
- Clear alert condition → Incident should auto-resolve.
- Confirm consistent mapping using checkID.
7. Troubleshooting
Incoming Payload Not Received
- Verify InfluxDB endpoint configuration.
- Check network connectivity.
- Confirm valid API token.
Incidents Not Auto-Resolving
- Verify InfluxDB is sending resolved events.
- Ensure same checkID in both firing and resolved payloads.
- Check Notification Rule includes recovery events.
Wrong or Missing Payload Fields
- Use Callgoose API logs to inspect exact payloads.
- Update API Filters to match JSON structure.
8. Conclusion
Integrating InfluxDB with Callgoose SQIBS enables fully automated incident creation and resolution for metric-driven alerts. By configuring InfluxDB webhook notifications and mapping them through Callgoose API Filters, teams gain real-time visibility into performance issues and resource anomalies.
This integration ensures that alert spikes instantly become actionable incidents, and clearing the alert automatically closes the incident lifecycle, improving operational reliability.
For further customization or advanced use cases, refer to the official documentation for both InfluxDB and Callgoose SQIBS:
