domotz_monitoring
Manage SNMP and TCP sensors on Domotz devices: list, create, delete sensors, view history, and configure triggers with alerts.
Instructions
Manage SNMP and TCP sensors (called "Eyes" in Domotz) on devices. Use the "action" parameter to select an operation. Requires agent_id and device_id for all actions.
ACTION REFERENCE:
list_snmp: List all SNMP sensors on a device
create_snmp: Create an SNMP sensor (needs body with OID config)
delete_snmp: Delete an SNMP sensor (needs sensor_id)
snmp_history: SNMP sensor value history over time (needs sensor_id, filterable by from/to)
snmp_trigger_functions: List available trigger functions for an SNMP sensor (needs sensor_id) — call this FIRST to get valid function_id values
list_snmp_triggers: List triggers configured on an SNMP sensor (needs sensor_id)
create_snmp_trigger: Create a trigger on an SNMP sensor (needs sensor_id + body with function_id and value)
delete_snmp_trigger: Delete a trigger (needs sensor_id + trigger_id)
create_snmp_trigger_alert: Activate alert notifications on a trigger (needs sensor_id + trigger_id + medium_name e.g. "email", "slack")
delete_snmp_trigger_alert: Remove alert notifications from a trigger (needs sensor_id + trigger_id + medium_name)
list_tcp: List TCP sensors on a device
create_tcp: Create a TCP sensor (needs body with port/host config)
delete_tcp: Delete a TCP sensor (needs service_id)
TRIGGER WORKFLOW (must follow these steps in order):
Call snmp_trigger_functions to get available function_ids (e.g. function_id=2 means "is greater than")
Call create_snmp_trigger with body containing function_id and value — VERIFY the response contains the created trigger before proceeding
Call create_snmp_trigger_alert with the trigger_id from step 2 to activate notifications — VERIFY the response confirms activation If ANY step returns an error, STOP and report the error to the user. Do NOT claim success without confirming each step's response.
GOTCHAS:
SNMP sensors and TCP sensors use different ID params: sensor_id for SNMP, service_id for TCP
Trigger creation requires a valid function_id from snmp_trigger_functions — do not guess function_ids
from/to on snmp_history accept ISO 8601 timestamps, default to last 7 days
TCP sensors do NOT support triggers or alerts
EXAMPLES:
List SNMP sensors: {"action": "list_snmp", "agent_id": 5, "device_id": 50}
Sensor history: {"action": "snmp_history", "agent_id": 5, "device_id": 50, "sensor_id": 3}
Get trigger functions: {"action": "snmp_trigger_functions", "agent_id": 5, "device_id": 50, "sensor_id": 3}
Create trigger (alert when value > 90): {"action": "create_snmp_trigger", "agent_id": 5, "device_id": 50, "sensor_id": 3, "body": {"function_id": 2, "value": "90"}}
Activate email alert on trigger: {"action": "create_snmp_trigger_alert", "agent_id": 5, "device_id": 50, "sensor_id": 3, "trigger_id": 1, "medium_name": "email"}
List TCP sensors: {"action": "list_tcp", "agent_id": 5, "device_id": 50}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End time for time series | |
| body | No | Request body (JSON object) | |
| from | No | Start time for time series | |
| action | Yes | The operation to perform | |
| agent_id | No | Agent/Collector ID | |
| device_id | No | Device ID | |
| sensor_id | No | SNMP Sensor ID | |
| service_id | No | TCP Service/Sensor ID | |
| trigger_id | No | Trigger ID | |
| medium_name | No | Alert medium name (e.g. email, slack) |