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 providing operations related to monitoring services on network devices. The "Get for Device" operation retrieves service information associated with a specified device, optionally filtered by service state or type.
This node is useful in scenarios where you want to programmatically access detailed service status data from devices monitored by LibreNMS. For example, it can be used to automate alerts, generate reports on service health per device, or integrate service status into broader network management workflows.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique ID of the device whose services you want to retrieve. |
| Filters | Optional filters to narrow down the services returned: |
| - State: Filter services by their state (OK, Warning, Critical). | |
| - Type: Filter services by their type using SQL LIKE pattern matching. |
Output
The node outputs JSON data representing the list of services for the specified device. Each service entry typically includes details such as service name, state, type, and other relevant metadata as provided by LibreNMS.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to a LibreNMS instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL and SSL certificate validation settings are configurable through credentials.
Troubleshooting
Common issues:
- Invalid or missing device identifier will result in no data or errors.
- Incorrect API credentials or URL misconfiguration may cause authentication failures.
- Filtering with unsupported values might return empty results.
Error messages:
- Authentication errors indicate invalid or missing API tokens; verify credentials.
- Network errors suggest connectivity issues to the LibreNMS server; check URL and network access.
- Empty responses when filtering may mean no services match the criteria; try broadening filters.
Links and References
If you need details on other resources or operations, feel free to ask!