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 to manage alerts among other resources. The "Unmute" operation for Alerts allows users to remove the mute status from a specific alert by its ID. This is useful in scenarios where an alert was previously silenced (muted) to avoid notifications during maintenance or investigation, and now needs to be reactivated to resume normal alerting.
Practical examples include:
- Automatically unmuting alerts after scheduled maintenance windows.
- Reactivating alerts that were muted due to false positives once the issue is resolved.
- Integrating with incident management workflows to control alert states programmatically.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The unique identifier of the alert to unmute |
Output
The node outputs JSON data representing the result of the unmute operation on the specified alert. Typically, this includes confirmation of the alert being unmuted or details about the alert's updated state. The exact structure depends on the LibreNMS API response but generally contains fields such as alert ID, status, and any relevant metadata.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a LibreNMS instance via its REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL and SSL certificate validation settings are configurable through credentials.
Troubleshooting
- Common issues:
- Invalid or missing Alert ID: Ensure the Alert ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the LibreNMS server is reachable from the n8n environment.
- Error messages:
- "Alert not found": The specified Alert ID does not exist; double-check the ID.
- "Unauthorized": API key is invalid or lacks permission; update credentials.
- SSL errors: If using self-signed certificates, enable skipping SSL validation in credentials.