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 "Get Outages" operation under the "Devices" resource in this LibreNMS node retrieves information about device outages within a specified date range. This is useful for network administrators who want to monitor device downtime, analyze outage patterns, or generate reports on device availability.
Typical use cases include:
- Fetching historical outage data for a specific device to investigate network reliability.
- Integrating outage information into dashboards or alerting systems.
- Auditing device performance over time by correlating outages with maintenance or incidents.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the device for which to retrieve outage information. |
| Date Range Options | Optional date range to filter outages. Includes: |
| - From Date | Start date (YYYY-MM-DD) to begin fetching outages from. |
| - To Date | End date (YYYY-MM-DD) to stop fetching outages at. |
Output
The node outputs JSON data representing the outages of the specified device within the given date range. The structure typically includes details such as outage start and end times, duration, and possibly the reason or status of each outage.
If binary data were involved (e.g., logs or reports), it would be summarized here, but this operation focuses on JSON outage records.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the node credentials.
- SSL certificate validation can be optionally disabled if using self-signed certificates.
Troubleshooting
Common issues:
- Invalid or missing device identifier will cause the API to return errors or empty results.
- Incorrect date formats for "From Date" or "To Date" may lead to request failures.
- Network connectivity problems or incorrect API URL/credentials will prevent successful data retrieval.
Error messages:
- "Device not found" — Verify the device hostname or ID is correct.
- "Invalid date format" — Ensure dates are in YYYY-MM-DD format.
- "Unauthorized" — Check that the API key credential is valid and has necessary permissions.
- "SSL certificate error" — If using self-signed certs, enable the option to allow unauthorized certificates.