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 allowing users to retrieve detailed information about individual alerts. This is useful in scenarios where network administrators want to programmatically fetch the status or details of a specific alert triggered by LibreNMS, enabling automated workflows such as incident management, notification dispatching, or further analysis.
For example, a user can configure this node to get the details of an alert by its ID and then use that data to create a ticket in an IT service management system or send a customized notification to a team chat.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The unique identifier of the alert to retrieve. This is required to specify which alert's details should be fetched. |
Output
The node outputs JSON data representing the details of the specified alert from LibreNMS. This typically includes fields such as alert status, description, timestamps, device information, and any other metadata associated with the alert.
If the alert contains any binary data (e.g., attachments or screenshots), the node would provide it in the binary output field; however, based on the provided code and context, the primary output is structured JSON data describing the alert.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the LibreNMS API must be set correctly in the credentials.
- Optionally, SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
- Common issues:
- Incorrect or missing Alert ID will cause the node to fail to retrieve alert data.
- Invalid or expired API credentials will result in authentication errors.
- Network connectivity problems or incorrect API base URL configuration can prevent successful communication with LibreNMS.
- Error messages:
- "Alert ID is required" — Ensure the Alert ID property is filled.
- "Authentication failed" — Verify API credentials and permissions.
- "Resource not found" or "404" — Confirm the Alert ID exists in LibreNMS.
- SSL errors — If using self-signed certificates, enable the option to skip SSL validation.