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 create a new service to be monitored on a device. This is useful in scenarios where network administrators want to add custom services (like ping, HTTP, TCP checks) for monitoring within LibreNMS, enabling proactive alerting and status tracking of those services.
For example, if you want to monitor a web server running on a specific device, you can create an HTTP service check by specifying the device, service type, IP address, and description. This helps ensure that the service is up and reachable, and any downtime or issues can trigger alerts.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or ID of the device on which the service will be monitored. |
| Service Type | The type of service to monitor, e.g., ping, http, tcp, etc. |
| IP Address | The IP address of the service to be monitored. |
| Description | A textual description of the service for identification purposes. |
| Additional Options | Optional parameters: - Parameters: Extra parameters for the service check. - Ignore: Whether to ignore this service in checks (boolean). |
Output
The node outputs JSON data representing the created service as returned by the LibreNMS API. This typically includes details such as the service ID, device association, type, IP address, description, and any other metadata provided by LibreNMS.
If the node supports binary data output, it would relate to any files or attachments returned by the API, but based on the provided code and context, the output is purely JSON.
Dependencies
- Requires connection to a LibreNMS instance via its REST API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the node credentials.
- Optionally, SSL certificate validation can be skipped based on credential settings.
Troubleshooting
Common Issues:
- Invalid device ID or hostname: Ensure the device exists in LibreNMS before creating a service.
- Incorrect service type: Use supported service types recognized by LibreNMS.
- Network connectivity problems: Verify that n8n can reach the LibreNMS API endpoint.
- Missing or invalid API credentials: Confirm that the API key/token is valid and has sufficient permissions.
Error Messages:
- Authentication errors usually indicate invalid or missing API credentials.
- Validation errors may occur if required fields like device, type, IP, or description are missing or malformed.
- API errors related to resource not found suggest the specified device does not exist.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring the LibreNMS instance is accessible.
Links and References
- LibreNMS Official Documentation
- LibreNMS API Documentation
- n8n documentation on creating custom nodes