Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
The "Set Maintenance" operation for the Devices resource in this node allows users to schedule maintenance windows on network devices monitored by LibreNMS. This is useful for temporarily suppressing alerts or notifications during planned downtime, upgrades, or troubleshooting activities on specific devices.
Typical use cases include:
- Scheduling a maintenance window before performing firmware updates on a device.
- Temporarily silencing alerts while investigating an issue.
- Coordinating maintenance periods across multiple devices to avoid alert noise.
For example, a user can specify a device by hostname or ID, set a maintenance duration (e.g., 2 hours), and optionally provide a title, notes, and start time for the maintenance event.
Properties
| Name | Meaning |
|---|---|
| Device | The target device identified by its hostname or unique device ID. |
| Duration | Length of the maintenance window in H:i format (e.g., "2:00" for 2 hours). |
| Additional Options | Optional parameters to customize the maintenance: |
| - Title | A descriptive title for the maintenance event. |
| - Notes | Additional notes or comments about the maintenance. |
| - Start Time | When the maintenance should begin, formatted as Y-m-d H:i:s (e.g., "2024-01-01 10:00:00"). |
Output
The node outputs JSON data representing the result of setting the maintenance window on the specified device. This typically includes confirmation details such as the maintenance ID, status, timestamps, and any messages returned by the LibreNMS API.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a LibreNMS instance with API access.
- An API authentication token or key credential must be configured in n8n to authorize requests.
- The base URL of the LibreNMS API must be provided in the credentials configuration.
- Proper permissions on the LibreNMS side to create or modify maintenance windows on devices.
Troubleshooting
- Invalid Device ID or Hostname: If the device identifier is incorrect or does not exist, the API will return an error. Verify the device name or ID before running the node.
- Incorrect Duration Format: The duration must be in
H:iformat. Providing an invalid format may cause the request to fail. - Start Time Format Issues: The optional start time must follow the
Y-m-d H:i:sformat exactly. Incorrect formatting can lead to errors or unexpected scheduling. - Authentication Errors: Ensure that the API key/token is valid and has sufficient privileges.
- API Connectivity Problems: Network issues or incorrect API URL configurations can prevent successful communication with LibreNMS.