Page tree
Skip to end of metadata
Go to start of metadata

The LibreNMS importer can be used to import devices from Libre to Unimus using the LibreNMS API.
If the importer is configured to run periodically on a schedule, this will effectively sync devices in your Libre instance to Unimus.

The importer supports syncing devices based on Device Groups. You have many options for Device Group membership filtering in Libre - so you can choose which devices get put into which groups.
You can therefore setup appropriate devices to automatically belong to specific groups in Libre, and import only desired devices into Unimus from these groups.

LibreNMS importer supports remote UUIDs.

How to configure the importer

1) Provide the full Libre server URL in the "LibreNMS server url" field.
For example: "".

2) Provide API token to access Libre.

3) Configure Device Groups, to import devices from, one per line.
 Device group must be configured in key value format e.g.  "group=GroupName" (without quotes)

4) Optionally, you can also schedule the importer.
You simply need to select an existing (or use the default) schedule.
With this configuration, Unimus will sync against Libre periodically.

Advanced settings

LibreNMS importer allows specifying the preferred field used for the address of imported devices via Address field priority setting.
'overwrite_ip -> hostname -> ip' tries to use the 'Overwrite IP' value of a host on LibreNMS as address of an imported device on Unimus falling back to 'Hostname' and then 'IP' if previous is not populated.
'overwrite_ip -> ip -> hostname' falls back to 'IP' and then 'Hostname'.

LibreNMS importer also allows specifying the preferred field for the description of imported devices via Description field priority setting.
'Description (purpose) -> Display name (display) -> sysName' tries to use the 'Description' value of a host on Zabbix as description of an imported device on Unimus falling back to 'Display name' and 'sysName' if previous is not populated.
'Display name (display) -> Description (purpose) -> sysName' and 'sysName -> Display name (display) -> Description (purpose)' work in analogous fashion.

  • No labels