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 functionality to retrieve alerts. The "Get All" operation under the "Alerts" resource fetches a list of alerts from LibreNMS, optionally filtered and ordered based on user-defined criteria.
This node is useful for network administrators and IT professionals who want to automate monitoring workflows by programmatically accessing alert data. For example, it can be used to pull all critical alerts or only those that are acknowledged, enabling integration with incident management systems or custom dashboards.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of optional filters to narrow down the alerts returned: |
| - State | Filter alerts by their state. Options: OK, Alert, Acknowledged |
| - Severity | Filter alerts by severity level. Options: OK, Warning, Critical |
| - Alert Rule ID | Filter alerts associated with a specific alert rule by its ID |
| - Order | Specify the order in which results are returned, e.g., "timestamp DESC" |
Output
The node outputs JSON data representing the list of alerts retrieved from LibreNMS. Each alert object typically contains details such as its state, severity, associated alert rule, timestamps, and other relevant metadata provided by LibreNMS.
There is no indication that this node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the LibreNMS API.
- The base URL for the LibreNMS instance must be configured in the credentials.
- The node expects the LibreNMS API v0 endpoint to be accessible.
- Optional configuration to allow skipping SSL certificate validation if using self-signed certificates.
Troubleshooting
- Common issues:
- Authentication failures due to incorrect or missing API key.
- Network connectivity problems to the LibreNMS server.
- Invalid filter values causing the API to reject requests.
- Error messages:
- Unauthorized errors indicate invalid or missing API credentials.
- Timeout or connection refused errors suggest network or server availability issues.
- Bad request errors may result from malformed filter parameters; verify filter values and formats.
Links and References
If you need further details about other operations or resources, feel free to ask!