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 providing operations related to network devices. The "Get Components" operation under the "Devices" resource retrieves detailed component information for a specified device by its hostname or ID. This is useful in scenarios where network administrators need to audit, monitor, or manage hardware components of devices within their network infrastructure.
Practical examples include:
- Fetching all hardware components (like CPUs, memory modules, power supplies) of a particular network device to check status or specifications.
- Integrating device component data into asset management or monitoring dashboards.
- Automating alerts or maintenance workflows based on component health or presence.
Properties
| Name | Meaning |
|---|---|
| Device | Device hostname or ID to identify which device's components to retrieve |
Output
The node outputs JSON data representing the components of the specified device. This typically includes details such as component types, statuses, identifiers, and other metadata relevant to each hardware component detected by LibreNMS.
If the node supports binary data output (not indicated here), it would generally represent files or images related to the device components, but this is not evident from the provided code.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the LibreNMS API must be set correctly in the credentials.
- SSL certificate validation can be optionally disabled based on credential settings.
Troubleshooting
Common issues:
- Incorrect device hostname or ID leading to no data returned.
- Authentication failures due to invalid or missing API tokens.
- Network connectivity problems between n8n and the LibreNMS server.
- SSL certificate errors if using self-signed certificates without allowing unauthorized certs.
Error messages and resolutions:
- Unauthorized or 401 errors: Verify that the API key credential is correct and has sufficient permissions.
- 404 Not Found: Check that the device identifier exists in LibreNMS.
- Connection timeout or network errors: Ensure the LibreNMS server is reachable from the n8n environment.
- SSL errors: Enable the option to allow unauthorized certificates if using self-signed certs.