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 Auth Logs" operation of the LibreNMS node retrieves authentication-related log entries from the LibreNMS network monitoring system. This operation is useful for network administrators and security analysts who want to monitor login attempts, track user authentications, or audit access events across devices managed by LibreNMS.
Typical use cases include:
- Auditing successful and failed login attempts on network devices.
- Investigating suspicious authentication activities.
- Generating reports on user access patterns over a specified time range.
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 retrieving results from (pagination). Default is 1. |
| Limit | Number of log entries to return per request. Default is 50. |
| From | Start date/time or event ID to begin fetching logs from. Format example: "2024-01-01 00:00:00". Optional. |
| To | End date/time or event ID to stop fetching logs at. Format example: "2024-01-31 23:59:59". Optional. |
| Sort Order | Sort order of the results, either Ascending or Descending. Default is Descending. |
Output
The node outputs JSON data containing the retrieved authentication log entries. Each entry typically includes details such as timestamp, device identifier, user information, event type, and status of the authentication attempt.
If binary data were involved (e.g., log file attachments), it would be summarized accordingly, but this operation focuses on JSON log data.
Dependencies
- Requires an active connection to a LibreNMS instance with API access.
- An API key credential must be configured in n8n to authenticate requests.
- The LibreNMS API base URL and SSL certificate validation settings are configured via credentials.
Troubleshooting
- Empty Results: If no logs are returned, verify that the device ID (if specified) is correct and that the date/time filters cover the period when logs exist.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access logs.
- Pagination Issues: If too many results are expected, adjust the "Limit" and "Start Page" options to paginate through all available logs.
- Date Format Errors: Use the correct date/time format ("YYYY-MM-DD HH:mm:ss") for the "From" and "To" fields to avoid query failures.