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 retrieve detailed information about a particular location within their network infrastructure. This is useful for network administrators who want to programmatically access location data such as site details or physical deployment points managed in LibreNMS.
A practical example would be automating the retrieval of location metadata to enrich network device records or to trigger workflows based on location-specific events or statuses.
Properties
| Name | Meaning |
|---|---|
| Location | The name or ID of the location to retrieve information for. This is a required string input where you specify which location's details you want to fetch. |
Output
The node outputs JSON data representing the details of the specified location from LibreNMS. This typically includes all relevant attributes stored in LibreNMS for that location, such as its identifier, name, description, and possibly associated metadata like address or coordinates.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the base URL of the LibreNMS instance configured in the credentials.
- The node uses the LibreNMS REST API v0 endpoints.
- SSL certificate validation can be optionally skipped based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing location ID/name will result in errors or empty responses.
- Incorrect API credentials or URL misconfiguration will cause authentication failures.
- Network connectivity issues to the LibreNMS server can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid API keys or insufficient permissions.
- "Location not found" errors suggest the provided location identifier does not exist.
- SSL errors may occur if the server uses self-signed certificates and the option to skip SSL validation is not enabled.
To resolve these:
- Verify the location ID or name is correct and exists in LibreNMS.
- Check API credentials and ensure they have proper access rights.
- Confirm the LibreNMS URL is reachable and correctly set.
- Enable skipping SSL validation if using self-signed certificates.