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 interacts with the LibreNMS network monitoring system, specifically providing functionality to retrieve graphical data related to port groups. The "Get Multi-Port Graph" operation fetches a graph representing multiple ports' data over a specified time range and with customizable dimensions.
This node is beneficial in scenarios where network administrators want to visualize performance or status metrics across several ports simultaneously. For example, it can be used to monitor traffic trends on multiple switch ports during a maintenance window or to compare utilization patterns across different interfaces.
Properties
| Name | Meaning |
|---|---|
| Port IDs | Comma-separated list of port IDs for which the graph will be generated (e.g., "1,2,3"). |
| Graph Options | Collection of optional parameters to customize the graph: |
| - From: Start time for the graph data (timestamp or datetime string). | |
| - To: End time for the graph data (timestamp or datetime string). | |
| - Width: Width of the graph image in pixels (default 1075). | |
| - Height: Height of the graph image in pixels (default 300). |
Output
The node outputs JSON data containing the graph information for the specified ports. This typically includes the graph image or URL representing the combined data of the requested ports over the selected time range and dimensions.
If binary data is returned (such as an image), it represents the visual graph illustrating port metrics.
Dependencies
- Requires connection to a LibreNMS instance with API access.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the LibreNMS API must be set correctly in the credentials.
- Optional SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
Common Issues:
- Invalid or missing port IDs may result in empty or error responses.
- Incorrect date/time formats for "From" and "To" parameters can cause request failures.
- Network connectivity issues or incorrect API URL configuration will prevent successful API calls.
- Insufficient permissions or invalid API tokens will lead to authorization errors.
Error Messages:
- "Unauthorized" — Check that the API token is valid and has necessary permissions.
- "Invalid port IDs" — Verify that the port IDs are correct and exist in LibreNMS.
- "Request timeout" — Ensure the LibreNMS server is reachable and responsive.
- "Invalid date format" — Confirm that the "From" and "To" fields use acceptable timestamp or datetime strings.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.