ahel
Start free

Atera Devices

SkillMonitoring & ops

Atera device monitors: HTTP, SNMP, and TCP monitor types for network devices, services, and applications, plus monitor configuration, thresholds, and polling behavior.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Atera Devices skill

What this skill tells your AI

The instructions your AI receives, as published by wyre-ai/msp-claude-plugins in msp-claude-plugins/atera/atera/skills/devices/SKILL.md and read by ahel’s review.

Overview

Atera device monitors extend monitoring capabilities beyond agent-based endpoints to include network devices, services, and applications. These agentless monitors use HTTP, SNMP, and TCP protocols to check availability and gather metrics.

Anti-triggers

  • A workstation or server running the Atera agent — that is an agent record, not a device monitor; use atera-agents. This is the single most common misroute in this plugin, because "device" means the managed endpoint in every other RMM here.
  • The alert a monitor fired — monitor configuration and thresholds live here; the acknowledge/resolve lifecycle is atera-alerts.
  • Network discovery, topology, or interface statistics as a product — use auvik-devices or auvik-networks; this skill only configures Atera's own HTTP, SNMP, and TCP checks.

Monitor Types

HTTP Monitors

Monitor web services and applications via HTTP/HTTPS requests.

FeatureDescription
ProtocolHTTP or HTTPS
MethodsGET, POST, HEAD
ValidationStatus code, response content
AuthenticationBasic, custom headers
Use CasesWebsites, APIs, web apps

SNMP Monitors

Monitor network devices using Simple Network Management Protocol.

FeatureDescription
VersionsSNMP v1, v2c, v3
OperationsGET, GETNEXT, WALK
Data TypesOIDs, MIBs, counters
Use CasesRouters, switches, firewalls, printers

TCP Monitors

Monitor service availability via TCP port connectivity.

FeatureDescription
ProtocolTCP
Check TypePort open/closed
ResponseConnection success/timeout
Use CasesCustom services, databases, mail servers

Device Monitor Fields

Common Fields

FieldTypeDescription
DeviceIDintUnique device identifier
CustomerIDintAssociated customer ID
CustomerNamestringCustomer display name
DeviceNamestringMonitor display name
DeviceTypestringHTTP, SNMP, TCP
HostnamestringTarget host/IP address
OnlinebooleanCurrent status
LastSeendatetimeLast successful check
CreatedOndatetimeMonitor creation date

HTTP-Specific Fields

FieldTypeDescription
URLstringFull URL to monitor
PortintHTTP port (default 80/443)
CheckCertificateExpirationbooleanMonitor SSL cert
CheckCertificateRevocationbooleanCheck cert revocation
UsernamestringBasic auth username
PasswordstringBasic auth password
ResponseTextstringExpected response content
ResponseCodeintExpected HTTP status

SNMP-Specific Fields (v1/v2c)

FieldTypeDescription
PortintSNMP port (default 161)
CommunitystringSNMP community string
OIDstringObject identifier to query
ThresholdstringAlert threshold
ThresholdComparisonstringComparison operator

SNMP v3-Specific Fields

FieldTypeDescription
UsernamestringSNMPv3 username
AuthProtocolstringMD5, SHA, SHA256, SHA384, SHA512
AuthPasswordstringAuthentication password
PrivProtocolstringDES, AES, AES192, AES256
PrivPasswordstringPrivacy password
ContextNamestringSNMPv3 context

TCP-Specific Fields

FieldTypeDescription
PortintTCP port to check
TimeoutintConnection timeout (ms)

API Patterns

List Generic Devices (Paginated)

GET /api/v3/devices/generic?page=1&itemsInPage=50
X-API-KEY: {api_key}

Response:

{
  "items": [
    {
      "DeviceID": 55555,
      "CustomerID": 12345,
      "CustomerName": "Acme Corporation",
      "DeviceName": "Core Router",
      "DeviceType": "SNMP",
      "Hostname": "192.168.1.1",
      "Online": true,
      "LastSeen": "2024-02-15T14:30:00Z"
    }
  ],
  "totalItems": 25,
  "page": 1,
  "itemsInPage": 50,
  "totalPages": 1
}

Create HTTP Monitor

POST /api/v3/devices/http
X-API-KEY: {api_key}
Content-Type: application/json

{
  "CustomerID": 12345,
  "DeviceName": "Website Monitor",
  "Hostname": "www.acme.com",
  "URL": "https://www.acme.com/health",
  "Port": 443,
  "CheckCertificateExpiration": true,
  "ResponseCode": 200,
  "ResponseText": "OK"
}

Response:

{
  "ActionID": 55556,
  "DeviceID": 55556
}

Create SNMP v1/v2c Monitor

POST /api/v3/devices/snmp
X-API-KEY: {api_key}
Content-Type: application/json

{
  "CustomerID": 12345,
  "DeviceName": "Core Router",
  "Hostname": "192.168.1.1",
  "Port": 161,
  "Community": "public",
  "OID": "1.3.6.1.2.1.1.3.0",
  "Threshold": "1000",
  "ThresholdComparison": ">"
}

Create SNMP v3 Monitor

POST /api/v3/devices/snmpv3
X-API-KEY: {api_key}
Content-Type: application/json

{
  "CustomerID": 12345,
  "DeviceName": "Firewall",
  "Hostname": "192.168.1.254",
  "Port": 161,
  "Username": "snmpuser",
  "AuthProtocol": "SHA256",
  "AuthPassword": "authpass123",
  "PrivProtocol": "AES256",
  "PrivPassword": "privpass123",
  "OID": "1.3.6.1.4.1.9.9.109.1.1.1.1.3.1",
  "Threshold": "80",
  "ThresholdComparison": ">"
}

Create TCP Monitor

POST /api/v3/devices/tcp
X-API-KEY: {api_key}
Content-Type: application/json

{
  "CustomerID": 12345,
  "DeviceName": "Database Server",
  "Hostname": "db.acme.local",
  "Port": 1433,
  "Timeout": 5000
}

Delete Device Monitor

DELETE /api/v3/devices/{deviceType}/{deviceId}
X-API-KEY: {api_key}

Device types: http, snmp, snmpv3, tcp, generic

Common SNMP OIDs

System Information

OIDDescription
1.3.6.1.2.1.1.1.0System description
1.3.6.1.2.1.1.3.0System uptime
1.3.6.1.2.1.1.5.0System name
1.3.6.1.2.1.1.6.0System location

Interface Statistics

OIDDescription
1.3.6.1.2.1.2.2.1.2Interface description
1.3.6.1.2.1.2.2.1.8Interface operational status
1.3.6.1.2.1.2.2.1.10Bytes in
1.3.6.1.2.1.2.2.1.16Bytes out

CPU and Memory

OIDDescription
1.3.6.1.4.1.9.9.109.1.1.1.1.3Cisco CPU 5 min avg
1.3.6.1.4.1.2021.10.1.3.1Linux 1 min load avg
1.3.6.1.4.1.2021.4.6.0Linux available RAM

Storage

OIDDescription
1.3.6.1.2.1.25.2.3.1.5Storage size
1.3.6.1.2.1.25.2.3.1.6Storage used

Common TCP Ports

PortServiceMonitor Name
21FTPFTP Server
22SSHSSH Access
25SMTPMail Server (SMTP)
53DNSDNS Server
80HTTPWeb Server
110POP3Mail Server (POP3)
143IMAPMail Server (IMAP)
443HTTPSSecure Web Server
445SMBFile Sharing
1433MSSQLSQL Server
3306MySQLMySQL Server
3389RDPRemote Desktop
5432PostgreSQLPostgreSQL
5900VNCVNC Server

Monitoring Best Practices

HTTP Monitors

  1. Use dedicated health endpoints - /health or /status
  2. Check SSL certificates - Enable cert expiration alerts
  3. Validate response content - Don't just check status codes
  4. Set reasonable timeouts - 10-30 seconds typical
  5. Monitor critical paths - Login, API endpoints

SNMP Monitors

  1. Use SNMPv3 when possible - Better security
  2. Change default community strings - Never use "public"
  3. Monitor interface status - Not just availability
  4. Set appropriate thresholds - Based on baseline
  5. Use meaningful OIDs - Document what you monitor

TCP Monitors

  1. Monitor service ports - Not just ICMP ping
  2. Use appropriate timeouts - Account for latency
  3. Monitor critical services - Databases, mail, etc.
  4. Document port purposes - Future reference

Error Handling

Common API Errors

CodeMessageResolution
400Invalid device IDVerify device exists
400Invalid hostnameCheck host/IP format
401UnauthorizedCheck API key
403ForbiddenVerify permissions
404Device not foundConfirm device ID
429Rate limitedWait and retry (700 req/min)

Monitor Configuration Errors

ErrorCauseResolution
Host unreachableNetwork issueVerify connectivity
SNMP timeoutWrong communityCheck SNMP config
Certificate errorInvalid/expired certUpdate certificate
Port closedService not runningStart service

Alerting Configuration

Threshold Types

ComparisonUsage
>Above threshold (CPU > 90%)
<Below threshold (disk free < 10%)
=Exact match
!=Not equal

Alert Intervals

SettingRecommendation
Check interval1-5 minutes
Alert after2-3 failures
Recovery after2-3 successes

Related Skills

Signals

GitHub stars
45
Forks
24
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
atera-devices
Source
github.com/wyre-ai/msp-claude-plugins

github.com/wyre-ai/msp-claude-plugins

More in Monitoring & ops

internal-comms
Skill · anthropicsagent-eval
Skill · affaan-magent-tracing
Skill · lobehubarchitecture-decision-records
Skill · affaan-mdashboard-builder
Skill · affaan-mdjango-celery
Skill · affaan-m