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 interacts with the LibreNMS network monitoring system to retrieve alert logs. Specifically, the "Get Alert Logs" operation fetches alert log entries from one or multiple devices monitored by LibreNMS. This is useful for network administrators who want to programmatically access alert history for troubleshooting, auditing, or integration with other systems.
Typical use cases include:
- Automatically retrieving recent alert logs for specific devices to monitor network health.
- Aggregating alert data across devices for reporting or dashboarding.
- Filtering alert logs by date/time range or pagination to handle large datasets efficiently.
Properties
| Name | Meaning |
|---|---|
| Device | Device hostname or ID to filter logs for a specific device. Optional; leave empty for all devices. |
| Options | Collection of optional parameters to refine the query: |
| Start Page | Page number to start fetching results from (pagination). Default is 1. |
| Limit | Number of alert log entries to return per request. Default is 50. |
| From | Start date/time or event ID to filter logs from. Format example: "2024-01-01 00:00:00". |
| To | End date/time or event ID to filter logs up to. Format example: "2024-01-31 23:59:59". |
| Sort Order | Sort order of results, either Ascending or Descending. Default is Descending. |
Output
The node outputs JSON data containing the retrieved alert logs. Each item in the output corresponds to an alert log entry with details such as timestamp, device information, alert message, severity, and other relevant metadata provided by LibreNMS.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a LibreNMS instance with API access enabled.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the credentials.
- Optionally, SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
- Empty results: Ensure the device ID/hostname is correct or try leaving it empty to fetch logs from all devices.
- Invalid date/time format: Use the exact format "YYYY-MM-DD HH:mm:ss" for the "From" and "To" fields.
- API authentication errors: Verify that the API key/token is valid and has sufficient permissions.
- Pagination issues: If too many results are returned, adjust the "Limit" and "Start Page" options to paginate through data.
- Network connectivity: Confirm that the LibreNMS server is reachable from the n8n environment.