Atera Device Monitoring

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.

Monitor Types

HTTP Monitors

Monitor web services and applications via HTTP/HTTPS requests.

SNMP Monitors

Monitor network devices using Simple Network Management Protocol.

TCP Monitors

Monitor service availability via TCP port connectivity.

Device Monitor Fields

Common Fields

HTTP-Specific Fields

SNMP-Specific Fields (v1/v2c)

SNMP v3-Specific Fields

TCP-Specific Fields

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

Interface Statistics

CPU and Memory

Storage

Common TCP Ports

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