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 retrieve detailed information about network devices. The "Get" operation under the "Devices" resource fetches data for a specified device by its hostname or ID. This is useful in scenarios where you need to monitor device status, gather inventory details, or automate network management tasks based on device attributes.
Practical examples include:
- Automatically retrieving device details before performing configuration changes.
- Monitoring device health and status as part of a larger workflow.
- Integrating device information into dashboards or reports.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the device to retrieve information for. |
Output
The node outputs JSON data representing the device's details as returned by the LibreNMS API. This typically includes device metadata such as hostname, IP addresses, status, hardware details, and other monitored parameters.
If the node supports binary data output (not indicated here), it would represent device-related files or logs, but this is not evident from the provided code.
Dependencies
- Requires an active connection to a LibreNMS instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL and SSL certificate validation settings are configurable through credentials.
Troubleshooting
Common issues:
- Invalid or missing device identifier will cause the API call to fail or return no data.
- Incorrect API credentials or URL misconfiguration can lead to authentication errors.
- Network connectivity problems between n8n and LibreNMS server may cause timeouts.
Error messages:
- Authentication failures usually indicate invalid API tokens or insufficient permissions.
- "Device not found" errors suggest the provided hostname or ID does not exist in LibreNMS.
- SSL certificate errors may occur if the LibreNMS server uses self-signed certificates without proper trust setup; enabling the option to skip SSL validation can help.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions.