Skip to content
Development
Skill

/devices

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

From plugin
msp-claude-plugins
52200 skills146 agents200 commands4 MCP

Claude Code

$ npx -y skills add wyre-ai/msp-claude-plugins --skill devices --agent claude-code

SKILL.md

devices.SKILL.md
name: "Atera Devices"
description: >
  Atera device monitors: HTTP, SNMP, and TCP monitor types for network
  devices, services, and applications, plus monitor configuration,
  thresholds, and polling behavior.
when_to_use: >-
  When configuring or troubleshooting Atera network and device monitors. Use
  when: atera device, atera monitor, http monitor, snmp monitor, tcp
  monitor, network monitor, device monitoring, snmp polling, uptime
  monitoring, or port monitor.

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.

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.

| Feature | Description | |---------|-------------| | **Protocol** | HTTP or HTTPS | | **Methods** | GET, POST, HEAD | | **Validation** | Status code, response content | | **Authentication** | Basic, custom headers | | **Use Cases** | Websites, APIs, web apps |

SNMP Monitors

Monitor network devices using Simple Network Management Protocol.

| Feature | Description | |---------|-------------| | **Versions** | SNMP v1, v2c, v3 | | **Operations** | GET, GETNEXT, WALK | | **Data Types** | OIDs, MIBs, counters | | **Use Cases** | Routers, switches, firewalls, printers |

TCP Monitors

Monitor service availability via TCP port connectivity.

| Feature | Description | |---------|-------------| | **Protocol** | TCP | | **Check Type** | Port open/closed | | **Response** | Connection success/timeout | | **Use Cases** | Custom services, databases, mail servers |

Device Monitor Fields

Common Fields

| Field | Type | Description | |-------|------|-------------| | `DeviceID` | int | Unique device identifier | | `CustomerID` | int | Associated customer ID | | `CustomerName` | string | Customer display name | | `DeviceName` | string | Monitor display name | | `DeviceType` | string | HTTP, SNMP, TCP | | `Hostname` | string | Target host/IP address | | `Online` | boolean | Current status | | `LastSeen` | datetime | Last successful check | | `CreatedOn` | datetime | Monitor creation date |

HTTP-Specific Fields

| Field | Type | Description | |-------|------|-------------| | `URL` | string | Full URL to monitor | | `Port` | int | HTTP port (default 80/443) | | `CheckCertificateExpiration` | boolean | Monitor SSL cert | | `CheckCertificateRevocation` | boolean | Check cert revocation | | `Username` | string | Basic auth username | | `Password` | string | Basic auth password | | `ResponseText` | string | Expected response content | | `ResponseCode` | int | Expected HTTP status |

SNMP-Specific Fields (v1/v2c)

| Field | Type | Description | |-------|------|-------------| | `Port` | int | SNMP port (default 161) | | `Community` | string | SNMP community string | | `OID` | string | Object identifier to query | | `Threshold` | string | Alert threshold | | `ThresholdComparison` | string | Comparison operator |

SNMP v3-Specific Fields

| Field | Type | Description | |-------|------|-------------| | `Username` | string | SNMPv3 username | | `AuthProtocol` | string | MD5, SHA, SHA256, SHA384, SHA512 | | `AuthPassword` | string | Authentication password | | `PrivProtocol` | string | DES, AES, AES192, AES256 | | `PrivPassword` | string | Privacy password | | `ContextName` | string | SNMPv3 context |

TCP-Specific Fields

| Field | Type | Description | |-------|------|-------------| | `Port` | int | TCP port to check | | `Timeout` | int | Connection 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",
Read more
@wyre-technology
Ships withmsp-claude-plugins

One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai

52200 skills146 agents4 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
52
Star history of wyre-technology/msp-claude-plugins on GitHub, a chart by star-history.com

Other skills on msp-claude-plugins.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills13d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react4d252k
@facebook@facebookInstall Skill

Questions about devices.

Which coding agents can use devices?
devices installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.