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, specifically to retrieve information about monitored services. The "Get All" operation under the "Services" resource fetches a list of all services being monitored by LibreNMS, optionally filtered by service state or type.
This node is useful in scenarios where you want to automate monitoring workflows, generate reports on service statuses, or trigger alerts based on service conditions. For example, you could use it to get all services currently in a critical state to notify your operations team or to audit all services of a certain type across your network.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the services retrieved: |
| - State | Filter services by their state. Options are: OK (0), Warning (1), Critical (2). |
| - Type | Filter services by their type using SQL LIKE syntax (string matching). |
Output
The node outputs JSON data representing an array of service objects retrieved from LibreNMS. Each object contains details about a monitored service, such as its current state, type, and other metadata provided by LibreNMS.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token credential configured in n8n for LibreNMS.
- The base URL and SSL certificate validation settings are configurable through credentials.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or missing API tokens.
- Network connectivity problems to the LibreNMS server.
- Invalid filter values causing no results or errors.
Error messages:
- Unauthorized or 401 errors indicate invalid API credentials; verify and update the API token.
- Connection timeout or DNS errors suggest network issues; check server availability and network configuration.
- Bad request errors may result from malformed filter parameters; ensure filters conform to expected types and formats.