Integrations
Monitor.us
Overview
This document provides a detailed guide to integrating Monitor.us with Callgoose SQIBS for real-time Incident Management, Incident Auto-Remediation, and Event-Driven Automation.
This integration enables automatic creation, updating, and resolution of incidents inside Callgoose SQIBS based on alerts generated in Monitor.us (e.g., Website Uptime Failures, Transaction Monitoring alerts, Server/CPU issues).
The guide includes steps for configuring webhooks in Monitor.us, defining JSON payloads, creating API filters in Callgoose SQIBS, testing, and troubleshooting.
Prerequisites
- Monitor.us account with permissions to configure alert notifications.
- Callgoose SQIBS account with permissions to create API Filters.
- Webhook/API Endpoint generated inside Callgoose SQIBS.
- API Token from Callgoose SQIBS.
1. Obtain API Token and Endpoint Details
To integrate with Callgoose SQIBS, first obtain an API token and endpoint URL.
1.1 Generate an API Token
Create an API token inside Callgoose SQIBS. Save it securely.
It will be appended to the webhook URL.
1.2 Find the API Endpoint
Your endpoint will follow the format:
https://****.callgoose.com/v1/process?from=MonitorUS&token=xxxx
Use the above URL as the destination for Monitor.us alert notifications.
2. Configuring Monitor.us to Send Alerts
Monitor.us supports custom webhook notifications for website uptime, server monitoring, and transaction monitoring alerts.
2.1 Access Monitor.us Dashboard
Log in to Monitor.us and ensure alerting is enabled for the monitors you wish to integrate.
2.2 Create a Webhook Notification
Navigate to:
Settings → Notifications → Add Alert Notification → Webhook
Configure the webhook:
- Name: Callgoose SQIBS
- Method: POST
- URL: Your API Endpoint from Step 1.2
- Content Type: application/json
- Send Recovery Alerts: Enable (required for auto-resolution)
Save the webhook.
2.3 Attach Webhook to Monitors
Open any monitor, such as:
- Website Uptime Monitor
- Port Monitor
- CPU/Memory Monitor
- Transaction Monitor
Under Alert Settings:
- Select Notification Method: Webhook
- Choose the Callgoose SQIBS webhook created above
- Save changes
2.4 Send Test Notification
Monitor.us provides a Send Test Alert option in webhook settings.
Verify that Callgoose SQIBS receives the test alert in the API Log.
3. Example JSON Payloads from Monitor.us
Monitor.us sends alerts using simple JSON events with status details, timestamps, and monitor metadata.
Below are the standard Monitor.us payload formats.
3.1 Triggered Alert Payload
{
"event_type": "alert",
"monitor_id": "981273",
"monitor_name": "Website Uptime",
"status": "DOWN",
"previous_status": "UP",
"severity": "critical",
"description": "Website is not reachable.",
"checked_at": "2025-01-10T12:30:00Z"
}
3.2 Resolved Alert Payload
{
"event_type": "alert",
"monitor_id": "981273",
"monitor_name": "Website Uptime",
"status": "UP",
"previous_status": "DOWN",
"severity": "info",
"description": "Website is reachable again.",
"checked_at": "2025-01-10T12:36:10Z"
}
4. Configuring Callgoose SQIBS
API filters are required to map incoming Monitor.us payloads to incidents.
4.1 Create API Filters
4.1.1 Trigger Filter (For Creating Incidents)
- Payload JSON Key: "status"
- Key Value Contains: DOWN
- Map Incident With: "monitor_id"
- Incident Title: "monitor_name"
- Incident Description: "description"
This ensures incidents are created when Monitor.us detects a DOWN state.
4.1.2 Resolve Filter (For Resolving Incidents)
- Payload JSON Key: "status"
- Key Value Contains: UP
- Incident Mapped With: "monitor_id"
This ensures automatic resolution when Monitor.us reports that the monitor recovered.
Refer to the API Filter Instructions and FAQ for more details.
5. Testing & Validation
5.1 Triggering Alerts
- Temporarily cause an outage for a monitored domain or service
- Monitor.us will send a DOWN alert
- Confirm that:
- Callgoose receives the payload
- An incident is created with the correct monitor_id
5.2 Resolving Alerts
- Restore the monitored service
- Monitor.us sends an UP alert
- Confirm the existing incident is auto-resolved in Callgoose SQIBS.
6. Debugging & Troubleshooting
- No Incident Created
- Verify the webhook URL is correct
- Ensure the Trigger Filter matches "status": "DOWN"
- Ensure the JSON keys exactly match Monitor.us payloads
- Check token validity
- Incident Not Resolving
- Ensure Monitor.us sends a "status": "UP" event
- Confirm the resolve filter maps using the same monitor_id
- Malformed JSON
- Monitor.us does not allow custom JSON modification
- Ensure no proxy or gateway modifies payloads
- Authentication Errors
- Verify token is correct in query string
- Confirm API endpoint is accessible over HTTPS
7. Security Considerations
- Keep your Callgoose API token private
- Use only HTTPS endpoints
- Rotate tokens periodically
- Restrict webhook usage inside Monitor.us to necessary monitors only
8. Conclusion
By following this guide, you can integrate Monitor.us with Callgoose SQIBS for seamless alerting, real-time incident creation, and automated resolution.
This workflow ensures continuous visibility across website uptime, server health, and transaction monitoring — all centrally managed inside Callgoose.
For additional internal references, consult:
