Help us improve
Share bugs, ideas, or general feedback.
From betterstack
Manages Better Stack uptime monitors: lists, creates, updates, pauses, deletes monitors, heartbeats, groups, and check types via API calls.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin betterstackHow this skill is triggered — by the user, by Claude, or both
Slash command
/betterstack:monitorsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Uptime monitors are the core of Better Stack's monitoring platform. They periodically check URLs, ports, or heartbeats to detect downtime and performance degradation. Monitors can be grouped, paused, and configured with custom check intervals, expected status codes, and alerting thresholds.
Provides API patterns for Better Stack MCP tools covering Uptime, Telemetry (Logtail), and Error Tracking: Bearer token auth, cursor pagination, rate limits, error handling.
Manages ConnectWise Automate monitors: configures thresholds, creates templates, assigns to computers. Covers internal, remote, SNMP types, alerts, and status evaluation.
Automates Uptimerobot operations via Composio toolkit through Rube MCP. Discovers tool schemas, manages connections, and executes monitor/alert workflows.
Share bugs, ideas, or general feedback.
Uptime monitors are the core of Better Stack's monitoring platform. They periodically check URLs, ports, or heartbeats to detect downtime and performance degradation. Monitors can be grouped, paused, and configured with custom check intervals, expected status codes, and alerting thresholds.
Better Stack supports check intervals from 30 seconds to 24 hours. Common intervals:
Heartbeat monitors expect periodic pings from your services. If a ping is missed, the monitor triggers an incident. Use for:
betterstack_list_monitors
Parameters:
page - Pagination cursorper_page - Results per page (default 50, max 100)Example response:
{
"data": [
{
"id": "12345",
"type": "monitor",
"attributes": {
"url": "https://example.com",
"pronounceable_name": "Example Website",
"monitor_type": "status",
"status": "up",
"check_frequency": 60,
"last_checked_at": "2026-03-27T10:00:00Z",
"paused": false
}
}
],
"pagination": {
"next": null,
"prev": null
}
}
betterstack_create_monitor
Parameters:
url - The URL or host to monitor (required)monitor_type - Type: status, ping, tcp, udp, dns, smtp, pop, imap (required)pronounceable_name - Human-readable namecheck_frequency - Check interval in seconds (default 180)expected_status_codes - Expected HTTP status codes (e.g., [200, 301])regions - Monitoring regions (us, eu, as, au)confirmation_period - Seconds to wait before confirming downtimemonitor_group_id - Assign to a monitor groupbetterstack_get_monitor
Parameters:
monitor_id - The monitor IDbetterstack_update_monitor
Parameters:
monitor_id - The monitor IDbetterstack_delete_monitor
Parameters:
monitor_id - The monitor IDbetterstack_pause_monitor
betterstack_resume_monitor
Parameters:
monitor_id - The monitor IDbetterstack_list_heartbeats
betterstack_create_heartbeat
Parameters:
name - Heartbeat name (required)period - Expected interval in seconds (required)grace - Grace period in seconds before alertingbetterstack_list_monitors to get all monitorsdown or validatingCause: Invalid monitor ID or monitor was deleted Solution: List monitors to verify the correct ID
Cause: URL format is incorrect or unreachable Solution: Verify the URL is valid and accessible from Better Stack's monitoring regions
Cause: A monitor for the same URL already exists Solution: Check existing monitors before creating; update the existing one instead