LibreNMS icon

LibreNMS

Interact with LibreNMS network monitoring system

Overview

The node integrates with the LibreNMS network monitoring system, specifically allowing management of network devices. The "Delete" operation under the "Devices" resource enables users to remove a device from the LibreNMS monitoring environment by specifying its hostname or device ID. This is useful for network administrators who want to clean up or decommission devices that are no longer in use or need to be removed from monitoring.

Practical examples include:

  • Automatically removing devices that have been decommissioned.
  • Cleaning up stale or duplicate device entries in LibreNMS.
  • Integrating device lifecycle management workflows where devices are deleted upon certain triggers.

Properties

Name Meaning
Device Device hostname or ID to delete from LibreNMS. This should be the unique identifier or hostname of the device you want to remove.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any error messages returned by the LibreNMS API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the LibreNMS API.
  • Needs the base URL of the LibreNMS instance configured in credentials.
  • The node uses the LibreNMS REST API v0 endpoints.
  • SSL certificate validation can be optionally skipped based on credential settings.

Troubleshooting

  • Common issues:

    • Providing an incorrect or non-existent device hostname/ID will likely cause the API to return an error indicating the device was not found.
    • Authentication failures if the API key or URL is misconfigured.
    • Network connectivity issues to the LibreNMS server.
    • SSL certificate errors if using self-signed certificates without allowing unauthorized certs.
  • Error messages and resolutions:

    • "Device not found" — Verify the device identifier is correct and exists in LibreNMS.
    • Authentication errors — Check that the API key credential is valid and has sufficient permissions.
    • SSL errors — Enable the option to allow unauthorized certificates if using self-signed certs or fix the certificate chain.
    • Network timeouts — Ensure the LibreNMS server is reachable from the n8n environment.

Links and References

Discussion