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
This node integrates with the LibreNMS network monitoring system, allowing users to interact programmatically with various LibreNMS resources. Specifically, for the Alert Rules - Get operation, it retrieves detailed information about a specific alert rule identified by its unique ID. This is useful in scenarios where you want to fetch configuration or status details of an alert rule to monitor network conditions, automate responses, or audit alert configurations.
Practical examples include:
- Fetching an alert rule's settings before updating or disabling it.
- Retrieving alert rule details to display in a custom dashboard.
- Automating checks on alert rules as part of a network health monitoring workflow.
Properties
| Name | Meaning |
|---|---|
| Rule ID | The unique identifier of the alert rule to retrieve. This is required to specify which alert rule's details should be fetched. |
Output
The node outputs JSON data representing the alert rule object corresponding to the provided Rule ID. This JSON typically includes all properties and configuration details of the alert rule as stored in LibreNMS, such as conditions, thresholds, notification settings, and metadata.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the alert rule, but this operation primarily returns structured JSON data.
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 of the LibreNMS API must be correctly set in the credentials.
- Optionally, SSL certificate validation can be skipped based on credential settings.
Troubleshooting
- Missing or invalid Rule ID: The node requires a valid alert rule ID. If omitted or incorrect, the API will likely return an error indicating the resource was not found.
- Authentication errors: Ensure the API key/token is valid and has sufficient permissions to access alert rules.
- Connection issues: Verify the LibreNMS URL is reachable and correct, including protocol (http/https).
- API version mismatch: The node uses LibreNMS API v0; ensure the LibreNMS instance supports this version.
- SSL errors: If using self-signed certificates, enable skipping SSL validation in credentials or provide proper certificates.