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 to retrieve event logs. Specifically, the "Get Event Logs" operation fetches system event log entries from LibreNMS, optionally filtered by device and time range. This is useful for network administrators who want to monitor or analyze events such as device status changes, alerts, or other logged activities within their network infrastructure.
Practical examples include:
- Retrieving recent event logs for a specific network device to troubleshoot connectivity issues.
- Collecting all event logs within a certain date range to audit network activity.
- Paginating through large sets of event logs for reporting or archival purposes.
Properties
| Name | Meaning |
|---|---|
| Device | Device hostname or ID to filter logs by a specific device. Optional; leave empty for all devices. |
| Options | Collection of optional parameters to refine the query: |
| - Start Page: Page number to start retrieving results from (pagination). | |
| - Limit: Number of log entries to return per request. | |
| - From: Start date/time or event ID to begin fetching logs from. | |
| - To: End date/time or event ID to stop fetching logs at. | |
| - Sort Order: Order in which results are sorted, either Ascending or Descending by timestamp. |
Output
The node outputs JSON data representing the retrieved event logs. Each item in the output corresponds to an individual event log entry containing details such as timestamps, event descriptions, device identifiers, and other relevant metadata provided by LibreNMS.
If binary data were involved (not indicated here), it would typically represent attachments or files related to logs, but this operation focuses on JSON event log data only.
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. Also verify the date/time filters are valid and that logs exist in that range.
- Authentication errors: Confirm the API token credential is valid and has sufficient permissions.
- Pagination issues: If too few or no results appear, check the "Start Page" and "Limit" values to ensure they cover the expected data range.
- Date format errors: Use the correct date/time format (
YYYY-MM-DD HH:mm:ss) when specifying "From" and "To" fields. - Connection errors: Verify the LibreNMS API URL is reachable and that SSL settings match your server configuration.