Integrations
LibreNMS
Overview
This document provides a detailed, step-by-step guide to integrating LibreNMS with Callgoose SQIBS for real-time network incident management, SNMP-based alerting, and automatic incident resolution.
The integration uses LibreNMS Alert Transports (Webhook/HTTP POST) to send alert payloads directly to Callgoose SQIBS. Callgoose API Filters interpret these payloads to automatically create incidents when alerts fire and resolve incidents when alerts recover.
Prerequisites
Before starting, ensure you have:
- A Callgoose SQIBS account with permission to create API Filters and access the process endpoint.
- A LibreNMS instance (self-hosted or containerized) with Admin access.
- A valid Callgoose API token and Api endpoint URL.
- At least one test alert rule in LibreNMS (recommended).
For Local Deployments
- Outbound internet access is required for webhook delivery to a cloud-hosted Callgoose SQIBS.
- Ensure DNS resolution for callgoose.com is correct.
- Firewall rules must allow outbound HTTPS (TCP 443) traffic.
1. Prepare Callgoose SQIBS
Use the Callgoose process endpoint with token authentication:
1.1 Obtain Callgoose API Endpoint
https://****.callgoose.com/v1/process?from=LibreNMS&token=xxxx
Store the API token securely. Do not hardcode it into public repositories.
2. Configure LibreNMS Webhook
2.1 Configure LibreNMS Alert Transport
- Navigate to Settings → Alerting → Alert Transports
- Click Create Transport
- Select Webhook
Enter the following details:
Webhook Transport Configuration
- Transport Name: Callgoose SQIBS
- Webhook URL: Callgoose endpoint from Section 1
- HTTP Method: POST
- Content Type: application/json
Save and enable the transport.
2.2 Assign Transport to Alert Rule
- Navigate to Alerting → Alert Rules
- Create or edit an alert rule
- Assign the Callgoose SQIBS Webhook Transport
- Enable the rule
LibreNMS will now send alert and recovery events to Callgoose.
3. LibreNMS Webhook Payload Structure
LibreNMS sends alert data using template variables defined in the webhook body.
Alert Firing (Problem Detected) Example
{
"alert_id": "1021",
"alert_name": "Device Down",
"device": "core-router-01",
"device_ip": "10.10.1.1",
"severity": "critical",
"rule": "Device status != up",
"message": "Device is unreachable",
"timestamp": "2025-12-03T10:15:00Z",
"status": "1"
}
Alert Resolve (Condition Normal) Example
{
"alert_id": "1021",
"alert_name": "Device Down",
"device": "core-router-01",
"device_ip": "10.10.1.1",
"severity": "ok",
"rule": "Device status != up",
"message": "Device recovered",
"timestamp": "2025-12-03T10:20:30Z",
"status": "0"
}
LibreNMS alert state values:
- 1 → Alert / Firing
- 0 → OK / Resolved
4. Create API Filters in Callgoose SQIBS
4.1 Trigger Filter — Create Incident
This filter creates a new incident when the LibreNMS alert fires.
- Payload JSON Key:"status"
- Key Value Contains: 1
- Map Incident With: "alert_id "(ensures the incident can be resolved later)
- Incident Title: "alert_name"
- Incident Description: "message"
4.2 Resolve Filter — Auto-Resolve Incident
This filter automatically resolves the corresponding incident in Callgoose when the LibreNMS alert clears.
- Payload JSON Key:" status"
- Key Value Contains: 0
- Incident Mapped With: "alert_id "(must match the trigger filter)
Refer to the API Filter Instructions and FAQ for more details.
5. Verify and Test Integration
- Trigger a LibreNMS alert (e.g., shut down an interface or device)
- Confirm webhook delivery in Callgoose → API Logs
- Verify incident creation when the alert fires
- Verify automatic resolution when the alert clears
6. Troubleshooting
6.1 No Payload Received in Callgoose
- Verify firewall allows outbound HTTPS (TCP 443)
- Check DNS resolution for callgoose.com
- Review LibreNMS alert transport logs
- Confirm the webhook URL and token are correct
6.2 Incidents Not Resolving Automatically
- Ensure LibreNMS sends recovery events (status = 0)
- Verify Resolve Filter configuration:
- Payload JSON Key: status
- Key Value Contains: 0
- Incident Mapped With: alert_id
6.3 Wrong Incident Title or Description
- Confirm Trigger Filter mappings:
- Incident Title → alert_name
- Incident Description → message
6.4 Duplicate Incidents Being Created
- Ensure the same mapping key is used:
- Trigger Filter → alert_id
- Resolve Filter → alert_id
7. Conclusion
Integrating LibreNMS with Callgoose SQIBS establishes a reliable, automated pipeline for network incident management.
This integration enables instant incident creation for network outages and threshold breaches, with automatic closure when conditions recover—providing centralized visibility and improved operational reliability.
