Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From atera
Creates threshold-based HTTP, TCP, or SNMP monitor for Atera agent via API. Validates agent existence and parameters, then returns monitor ID and config summary.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin ateraHow this command is triggered — by the user, by Claude, or both
Slash command
/atera:create-monitorThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Create Atera Monitor Create a threshold-based monitor for an agent including HTTP, TCP, or SNMP monitoring. ## Prerequisites - Valid Atera API key configured - Agent must exist and be online - User must have monitor creation permissions ## Steps 1. **Validate agent exists** - Verify agent exists - Capture device and customer info 2. **Validate monitor parameters** - Check monitor_type is valid (HTTP, TCP, SNMP) - Validate target format based on type - Set defaults for optional parameters 3. **Create the monitor** Based on monitor_type: For HTTP: Fo...
/create-monitorCreates a new Better Stack uptime monitor for a URL or host with optional check type (http, ping, tcp, etc.), frequency, name, and expected status. Returns monitor ID.
/site-overviewGenerates health overview for a Domotz site by agent ID, including agent status, device counts, active alerts, sensor health, overall score, and action recommendations.
/monitorConfigures monitoring dashboards, metrics collection, and alerting rules for a target using Datadog (default), CloudWatch, Prometheus, or Grafana.
/setup-synthetic-monitoringSets up synthetic monitoring for application uptime, transactions, APIs, multi-location tests, and SSL certs; produces configs, test scripts, alerts, dashboards, and response playbooks.
/create-alertsCreates alerting rules for latency, errors, throughput, resources, availability, and SLO violations. Outputs Prometheus/Datadog configs, thresholds with rationale, routing, escalation, runbooks, and testing.
/monitor-errorsSets up error monitoring and alerting for HTTP errors, app exceptions, DB failures, external APIs, jobs, and client-side issues. Provides tool configs (Sentry/Rollbar/CloudWatch), alerts, dashboards, error budgets, and guidelines.
Share bugs, ideas, or general feedback.
Create a threshold-based monitor for an agent including HTTP, TCP, or SNMP monitoring.
Validate agent exists
curl -s -X GET "https://app.atera.com/api/v3/agents/{agent_id}" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Accept: application/json"
Validate monitor parameters
Create the monitor Based on monitor_type:
For HTTP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/http" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"Name": "<name>",
"URL": "<target>",
"Interval": <interval>,
"AlertSeverity": "<alert_severity>"
}'
For TCP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/tcp" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"Name": "<name>",
"Port": <target>,
"Interval": <interval>,
"AlertSeverity": "<alert_severity>"
}'
For SNMP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/snmp" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"Name": "<name>",
"OID": "<target>",
"Threshold": "<threshold>",
"Interval": <interval>,
"AlertSeverity": "<alert_severity>"
}'
Return monitor confirmation
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| agent_id | integer | Yes | - | The agent ID to monitor |
| monitor_type | string | Yes | - | HTTP, TCP, or SNMP |
| name | string | Yes | - | Monitor display name |
| target | string | Yes | - | URL, port, or OID to monitor |
| interval | integer | No | 5 | Check interval in minutes |
| threshold | string | No | - | Alert threshold value |
| alert_severity | string | No | Warning | Information, Warning, Critical |
/create-monitor 12345 --monitor_type HTTP --name "Website Check" --target "https://example.com"
/create-monitor 12345 --monitor_type HTTP --name "Website Check" --target "https://example.com" --interval 5
/create-monitor 12345 --monitor_type TCP --name "SQL Port" --target "1433"
/create-monitor 12345 --monitor_type TCP --name "SQL Port" --target "1433" --alert_severity Critical
/create-monitor 12345 --monitor_type SNMP --name "CPU Usage" --target "1.3.6.1.2.1.25.3.3.1.2" --threshold "90"
/create-monitor 12345 --monitor_type SNMP --name "Disk Usage" --target "1.3.6.1.2.1.25.2.3.1.5" --threshold "80" --interval 10 --alert_severity Warning
Monitor Created Successfully
Monitor ID: 9876
Type: HTTP
Name: Website Check
Agent: SERVER-WEB01 (ID: 12345)
Customer: Acme Corporation
Configuration:
- URL: https://example.com
- Interval: 5 minutes
- Alert Severity: Warning
- Expected Response: 200 OK
Status: Active
First check scheduled in 5 minutes
Monitor Created Successfully
Monitor ID: 9877
Type: TCP
Name: SQL Port
Agent: SERVER-SQL01 (ID: 12345)
Customer: Acme Corporation
Configuration:
- Port: 1433
- Interval: 5 minutes
- Alert Severity: Critical
Status: Active
Monitoring for port connectivity
Monitor Created Successfully
Monitor ID: 9878
Type: SNMP
Name: CPU Usage
Agent: SERVER-DC01 (ID: 12345)
Customer: Acme Corporation
Configuration:
- OID: 1.3.6.1.2.1.25.3.3.1.2
- Threshold: 90
- Interval: 5 minutes
- Alert Severity: Warning
Status: Active
Alert when value exceeds threshold
Agent not found: 12345
Please verify the agent ID and try again.
Use /search-agents to find valid agent IDs.
Agent is offline: DESKTOP-ABC123 (ID: 12345)
Last seen: 2026-02-03 18:45:00 (16 hours ago)
Monitor can be created but won't collect data until agent is online.
Proceed? [Y/n]
Invalid monitor type: "PING"
Valid monitor types:
- HTTP: Monitor website or API endpoints
- TCP: Monitor port connectivity
- SNMP: Monitor SNMP metrics with thresholds
Invalid URL: "example.com"
HTTP monitors require a full URL:
- https://example.com
- http://192.168.1.100:8080/health
Invalid port: "sql"
TCP monitors require a numeric port:
- 1433 (SQL Server)
- 3389 (RDP)
- 443 (HTTPS)
Invalid OID format: "cpu.usage"
SNMP monitors require a valid OID:
- 1.3.6.1.2.1.25.3.3.1.2 (CPU)
- 1.3.6.1.2.1.25.2.3.1.5 (Storage)
Monitor already exists for this target
Existing Monitor:
ID: 9870
Name: Website Check
Target: https://example.com
Create anyway? [y/N]
Rate limit exceeded (700 req/min)
Waiting 30 seconds before retry...
GET /api/v3/agents/{agentId}
X-API-KEY: {api_key}
POST /api/v3/agents/{agentId}/monitors/http
X-API-KEY: {api_key}
Content-Type: application/json
{
"Name": "Website Check",
"URL": "https://example.com",
"Interval": 5,
"AlertSeverity": "Warning"
}
POST /api/v3/agents/{agentId}/monitors/tcp
X-API-KEY: {api_key}
Content-Type: application/json
{
"Name": "SQL Port",
"Port": 1433,
"Interval": 5,
"AlertSeverity": "Critical"
}
POST /api/v3/agents/{agentId}/monitors/snmp
X-API-KEY: {api_key}
Content-Type: application/json
{
"Name": "CPU Usage",
"OID": "1.3.6.1.2.1.25.3.3.1.2",
"Threshold": "90",
"Interval": 5,
"AlertSeverity": "Warning"
}
| Metric | OID |
|---|---|
| CPU Usage | 1.3.6.1.2.1.25.3.3.1.2 |
| Memory Usage | 1.3.6.1.2.1.25.2.3.1.5 |
| Disk Usage | 1.3.6.1.2.1.25.2.3.1.6 |
| Interface Status | 1.3.6.1.2.1.2.2.1.8 |
| System Uptime | 1.3.6.1.2.1.1.3.0 |
/search-agents - Search for RMM agents/list-alerts - View monitor alerts/resolve-alert - Resolve monitor alerts