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 functionality to retrieve the availability status of a specified network device. This operation is useful for network administrators who want to monitor device uptime and downtime over a given period. For example, it can be used to generate reports on device reliability or to trigger alerts if a device has been unavailable during critical times.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the network device whose availability is queried. |
| Date Range Options | Optional date range specifying the start ("From Date") and end ("To Date") dates (YYYY-MM-DD) to filter the availability data. |
- Device: Required string input where you specify the target device by its hostname or ID.
- Date Range Options: A collection allowing optional filtering of availability data between two dates. Both "From Date" and "To Date" are strings in
YYYY-MM-DDformat.
Output
The node outputs JSON data representing the availability information of the specified device within the optional date range. The exact structure depends on the LibreNMS API response but typically includes timestamps, availability percentages, and possibly outage details.
If binary data were involved (not indicated here), it would represent raw files or logs related to device availability, but this node focuses on JSON data output.
Dependencies
- Requires connection to a LibreNMS instance via its REST API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL and SSL certificate validation settings must be properly set in the node credentials.
Troubleshooting
Common Issues:
- Invalid or missing device identifier will cause the API call to fail.
- Incorrect date formats in the "From Date" or "To Date" fields may result in errors or no data returned.
- Network connectivity issues or incorrect API credentials will prevent successful communication with LibreNMS.
Error Messages:
- "Device not found": Verify the device hostname or ID is correct and exists in LibreNMS.
- "Invalid date format": Ensure dates are in
YYYY-MM-DDformat. - Authentication errors: Check that the API key/token is valid and has sufficient permissions.