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 node integrates with the LibreNMS network monitoring system, specifically allowing users to update device information. This operation is useful for network administrators who need to modify device attributes such as hostname, location, or any other configurable field within LibreNMS. For example, if a device's IP address or description changes, this node can update that information programmatically, ensuring the monitoring system stays current without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the device to update. |
| Field | The specific field name on the device record that you want to update. |
| Value | The new value to assign to the specified field. |
Output
The node outputs JSON data representing the updated device object as returned by the LibreNMS API after the update operation. This typically includes the device's current state with all its fields, reflecting the changes made. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the LibreNMS API.
- The node expects the LibreNMS instance URL and authentication details to be configured in the credentials.
- Network connectivity to the LibreNMS server is necessary.
- The base URL for API requests is derived from the provided credentials, with SSL certificate validation optionally disabled based on configuration.
Troubleshooting
Common Issues:
- Incorrect device identifier: If the device hostname or ID does not exist, the update will fail.
- Invalid field name: Specifying a field that LibreNMS does not recognize will cause an error.
- Authentication failure: Missing or invalid API credentials will prevent successful communication.
- Network issues: Connectivity problems to the LibreNMS server will result in request failures.
Error Messages:
- "Device not found": Verify the device identifier is correct.
- "Invalid field" or similar: Check that the field name matches one supported by LibreNMS.
- "Unauthorized" or "Authentication failed": Confirm API credentials are valid and have sufficient permissions.
- SSL errors: If using self-signed certificates, ensure the option to allow unauthorized certificates is enabled.