Help us improve
Share bugs, ideas, or general feedback.
From domotz
Provides guidance and API patterns for Domotz Eyes sensors including TCP connectivity tests, HTTP requests, custom checks, latency tracking, and service availability monitoring.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin domotzHow this skill is triggered — by the user, by Claude, or both
Slash command
/domotz:eyesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Domotz Eyes are synthetic monitoring sensors that run from Domotz agents to actively test service availability and performance. Unlike passive SNMP monitoring, Eyes actively probe endpoints with TCP connections, HTTP requests, and custom checks to verify services are responding correctly.
Guides Domotz MCP tools for network monitoring agents, devices, alerts, scans, SNMP, ports, speed tests: API key auth, regions, structure, pagination, rate limits, error handling.
Configures and manages Atera device monitors using HTTP, SNMP, and TCP protocols for network devices, services, and applications. Covers types, fields, thresholds, and MSP best practices.
Manages ConnectWise Automate monitors: configures thresholds, creates templates, assigns to computers. Covers internal, remote, SNMP types, alerts, and status evaluation.
Share bugs, ideas, or general feedback.
Domotz Eyes are synthetic monitoring sensors that run from Domotz agents to actively test service availability and performance. Unlike passive SNMP monitoring, Eyes actively probe endpoints with TCP connections, HTTP requests, and custom checks to verify services are responding correctly.
TCP Eyes establish a TCP connection to a specified host and port:
HTTP Eyes send HTTP/HTTPS requests and validate responses:
| Status | Meaning |
|---|---|
UP | Check passed successfully |
DOWN | Check failed (connection refused, timeout, wrong response) |
WARNING | Check passed but latency exceeds threshold |
domotz_list_eyes
Parameters:
agent_id -- The agent running the sensors (required)Example response:
[
{
"id": 101,
"name": "Web Server HTTPS",
"type": "http",
"target": "https://app.acmecorp.com",
"status": "UP",
"latency_ms": 145,
"last_check": "2026-03-27T15:30:00Z",
"interval_seconds": 300
},
{
"id": 102,
"name": "Database Port",
"type": "tcp",
"target": "192.168.1.50:5432",
"status": "UP",
"latency_ms": 2,
"last_check": "2026-03-27T15:30:00Z",
"interval_seconds": 60
}
]
domotz_get_eye
Parameters:
agent_id -- The agent ID (required)eye_id -- The specific eye/sensor ID (required)domotz_list_eye_results
Parameters:
agent_id -- The agent ID (required)eye_id -- The eye/sensor ID (required)Example response:
[
{
"timestamp": "2026-03-27T15:30:00Z",
"status": "UP",
"latency_ms": 145,
"http_status_code": 200
},
{
"timestamp": "2026-03-27T15:25:00Z",
"status": "UP",
"latency_ms": 152,
"http_status_code": 200
}
]
domotz_list_agents to get all sitesdomotz_list_eyesdomotz_list_eye_results for a specific sensorCause: Target service is unreachable, firewall blocking, or service crashed Solution: Check device status; verify service is running; check firewall rules
Cause: Network congestion, server overload, or WAN issues Solution: Check speed test results; review SNMP data for network devices; check server resources
Cause: Eye was recently created, agent is offline, or eye is disabled Solution: Verify agent is online; check eye configuration; wait for first check cycle