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 acknowledge alerts. Acknowledging an alert marks it as recognized by a user or system, optionally adding a note and controlling whether the alert should re-notify if its status changes.
This operation is useful in scenarios where network administrators want to track which alerts have been seen and handled, preventing repeated notifications for the same issue unless it worsens or improves. For example, after investigating a network fault indicated by an alert, an admin can acknowledge it with a note explaining the action taken.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The unique identifier of the alert to acknowledge. |
| Acknowledge Options | Collection of optional parameters: • Note: A text note to add to the alert. • Until Clear: Boolean flag indicating whether to re-alert if the alert changes (true/false). |
Output
The node outputs JSON data representing the result of the acknowledge operation on the specified alert. This typically includes confirmation details such as the updated alert status and any notes added.
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 to authorize requests.
- The base URL and SSL certificate validation settings are configurable through credentials.
Troubleshooting
- Invalid Alert ID: If the provided alert ID does not exist, the node may return an error indicating the alert was not found. Verify the alert ID is correct.
- Authentication Errors: Failure to authenticate with the LibreNMS API will cause errors. Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the LibreNMS server can cause timeouts or connection errors. Check network access and URL correctness.
- Permission Denied: If the API user lacks permission to acknowledge alerts, the operation will fail. Confirm user roles and privileges in LibreNMS.