Integrations
Mera Monitor
Overview
This document provides a detailed guide to integrating Mera Monitor with Callgoose SQIBS for real-time Incident Management, alert-based incident creation, and automated resolution.
The integration uses Mera Monitor Webhooks to send alert event payloads directly to Callgoose SQIBS, 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.
- A Mera Monitor workspace with admin-level access to alert rules and webhook settings.
- A valid Callgoose API token and API endpoint URL.
- A test alert configured in Mera Monitor for validating webhook delivery and payload field mapping.
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=MeraMonitor&token=xxxx
Store the API token securely and never commit it to source control.
2. Configure Mera Monitor Webhook
2.1 Choose the Webhook Scope
Mera Monitor allows creating webhooks at:
- Global Notification Channel level
- Project-level Alert Rule level
Webhook location varies depending on how alerts are organized inside Mera Monitor.
2.2 Configure Webhook Fields
Fill in the following fields:
- Webhook URL: Use the Callgoose endpoint generated in Step 1.
- HTTP Method: POST
- Content Type: application/json
- Send Resolved Alerts: Must be enabled for full auto-resolution support inside Callgoose.
Save and enable the webhook.
2.3 Verification Headers
Depending on your configuration, Mera Monitor may send security headers such as:
- X-Mera-Signature – Signature for payload integrity
- X-Mera-Event – Event type
- X-Mera-Source – Which monitoring module generated the alert
If using a proxy or external receiver, verify these headers before forwarding to Callgoose.
3. Example Mera Monitor Payloads
3.1 Firing State Payload
{
"status": "firing",
"alert_id": "mm-alert-7281",
"alert_name": "High CPU Usage",
"severity": "critical",
"description": "CPU usage crossed 90% for more than 2 minutes",
"timestamp": "2025-10-01T12:20:33Z",
"labels": {
"host": "server-01",
"region": "in-mum-1"
},
"metrics": {
"cpu_used": 95
}
}
3.2 Resolved State Payload
{
"status": "resolved",
"alert_id": "mm-alert-7281",
"alert_name": "High CPU Usage",
"resolved_at": "2025-10-01T12:28:11Z"
}
Use Callgoose’s API Logs to inspect the exact payload structure for your environment.
4. Create API Filters in Callgoose SQIBS
Callgoose API Filters convert incoming Mera Monitor webhooks into incidents.
Use two filters:
- Trigger Filter (create incident)
- Resolve Filter (auto-resolve)
4.1 Trigger Filter — Create Incident
- Payload JSON Key: "status"
- Key Value Contains: firing
- Map Incident With: "alert_id"
- Incident Title: "alert_name"
- Incident Description: "description" (optional — leave empty to use the full JSON)
This filter creates an incident whenever Mera Monitor fires a new alert.
4.2 Resolve Filter — Auto-Resolve Incident
- Payload JSON Key: "status"
- Key Value Contains: resolved
- Incident Mapped With: "alert_id"
This ensures that incidents are resolved automatically when Mera Monitor sends a resolve event. Refer to the API Filter Instructions and FAQ for more details.
5. Verify and Test the Integration
5.1 Test Initial Delivery
- Create a broad test filter in Callgoose.
- Trigger a test webhook from Mera Monitor.
- Confirm that Callgoose receives the payload in API Logs.
5.2 View Exact Payload
Use Callgoose API Logs to inspect the raw JSON payload from Mera Monitor.
Copy field names directly from the payload to ensure correct mappings.
5.3 Final Verification
- Trigger an alert in Mera Monitor → Incident should be created.
- Clear the alert → Incident should auto-resolve.
- Ensure correct mapping using alert_id.
6. Troubleshooting
Incoming Payload Not Received
- Check Mera Monitor webhook logs.
- Verify endpoint URL and token.
- Ensure no filter mismatch in Callgoose.
- Confirm network connectivity.
Incidents Not Auto-Resolving
- Verify Mera Monitor sends "status": "resolved".
- Ensure the same alert_id is used for both firing and resolved events.
- Confirm "Send Resolved Alerts" is enabled.
Wrong or Missing Payload Fields
- Inspect live payloads in Mera Monitor webhook logs.
- Update API Filters to match exact field names.
- Re-run firing + resolved alert tests.
7. Conclusion
Integrating Mera Monitor with Callgoose SQIBS enables automated incident creation and resolution based on alert events. By configuring Mera Monitor webhooks and mapping them through Callgoose API Filters, teams gain real-time visibility into monitoring issues, performance thresholds, and system anomalies.
With clean Trigger and Resolve filters, your incident lifecycle becomes fully automated—ensuring faster response and improved operational reliability.
For further customization or advanced use cases, refer to the official documentation for both Mera Monitor and Callgoose SQIBS:
