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 system logs, specifically syslog entries in this case. It allows users to fetch syslog data from one or multiple devices monitored by LibreNMS, supporting filtering and pagination options. This is useful for network administrators who want to analyze device logs for troubleshooting, auditing, or monitoring network events.
Practical examples:
- Fetching recent syslog messages from a specific network device to diagnose connectivity issues.
- Retrieving all syslog entries within a certain time range to audit network activity.
- Paginating through large volumes of syslog data to process logs incrementally.
Properties
| Name | Meaning |
|---|---|
| Device | Device hostname or ID to filter logs for a specific device. Leave empty to get logs from all devices. |
| Options | Collection of optional parameters to control the query: |
| - Start Page: Page number to start retrieving results from (default 1). | |
| - Limit: Number of log entries to return per request (default 50). | |
| - From: Start date/time or event ID to filter logs from (e.g., "2024-01-01 00:00:00"). | |
| - To: End date/time or event ID to filter logs until (e.g., "2024-01-31 23:59:59"). | |
| - Sort Order: Order to sort results, either Ascending or Descending (default Descending). |
Output
The node outputs JSON data containing the retrieved syslog entries. Each entry typically includes details such as timestamp, device identifier, log message, severity, and other relevant metadata depending on LibreNMS's API response structure.
If binary data were supported (not indicated here), it would represent raw log files or attachments, but this node focuses on JSON-formatted syslog data.
Dependencies
- Requires an active LibreNMS instance accessible via its REST API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL and SSL certificate validation settings are configurable via credentials.
Troubleshooting
- Empty results: Verify that the device ID or hostname is correct if filtering by device. Also check the date/time range filters to ensure they cover the expected log period.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access logs.
- API connection issues: Confirm the LibreNMS URL is reachable from the n8n environment and SSL settings match the server configuration.
- Pagination confusion: If not all logs appear, adjust the "Start Page" and "Limit" options to paginate through results properly.