LibreNMS icon

LibreNMS

Interact with LibreNMS network monitoring system

Overview

The node integrates with the LibreNMS network monitoring system, specifically allowing users to create new location entries within LibreNMS. This is useful for network administrators who want to organize and manage physical or logical locations of their network devices. By creating locations, users can better categorize devices geographically or by site, improving monitoring and reporting.

A practical example would be adding a new office site or data center location with its geographic coordinates so that devices assigned to that location can be tracked accordingly.

Properties

Name Meaning
Location Name The name of the location to create in LibreNMS (e.g., "New York Office").
Coordinates A collection of coordinate details:
- Latitude Latitude coordinate of the location (e.g., "37.4220041").
- Longitude Longitude coordinate of the location (e.g., "-122.0862462").
- Fixed Coordinates Boolean indicating if the coordinates are fixed or can be updated from the device.

Output

The node outputs JSON data representing the newly created location object as returned by the LibreNMS API. This typically includes the location's ID, name, coordinates, and any other metadata provided by LibreNMS.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON.

Dependencies

  • Requires an active connection to a LibreNMS instance.
  • Needs an API key credential configured in n8n for authenticating requests to LibreNMS.
  • The base URL of the LibreNMS API must be set in the credentials.
  • Optionally, SSL certificate validation can be skipped based on credential settings.

Troubleshooting

  • Invalid Credentials: If the API key or URL is incorrect, the node will fail to authenticate. Verify the API key and URL in the credentials.
  • Missing Required Fields: The "Location Name" is required; omitting it will cause errors.
  • Coordinate Format Issues: Latitude and longitude should be valid strings representing decimal degrees. Invalid formats may cause API rejection.
  • API Endpoint Errors: Ensure the LibreNMS API endpoint is reachable and the user has permissions to create locations.
  • SSL Certificate Errors: If using self-signed certificates, enable skipping SSL validation in credentials.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion