Device Sync platforms at a glance
Every driver uses the same pipeline, matching rules and Problem Devices tab, described in How Device Sync decides. What differs is how each platform carries the Device Profile reference, what you can filter on, and how much field experience the driver has.
Comparison
| Platform | Kind | Device Profile reference | Filters | From | Status |
|---|---|---|---|---|---|
| NetBox | Source of truth | Tag rconfig::device_profile::<slug> |
Tag, site, status | V8.2.0 | Field tested |
| Nautobot | Source of truth | Custom field rconfig_device_profile |
Tag, site, status | V8.2.0 | Field tested |
| Infrahub | Source of truth | None per device: instance default only | In the GraphQL query | V8.2.0 | Lab tested |
| Zabbix | Monitoring | Host tag rconfig::device_profile = slug |
Host groups, hosts, status, maintenance | V8.2.0 | Field tested |
| Checkmk | Monitoring | Host label rconfig: device_profile--<slug> |
Folder, label, attribute, site | V8.2.0 | Field tested |
| PRTG | Monitoring | Tag rconfig::device_profile::<slug> |
Status, tags, name | V8.2.0 | Lab tested |
| Statseeker | Monitoring | Group or tag rconfig::device_profile::<slug> |
Name, group, status | V8.2.0 | Field tested |
| LibreNMS | Monitoring | Device group rconfig::device_profile::<slug> |
Device group, OS, type, location | V8.4.2 | Lab tested |
| Observium | Monitoring | Device group rconfig::device_profile::<slug> |
Device group, OS, type, location | V8.4.2 | Unverified |
| OpenNMS | Monitoring | Surveillance category rconfig::device_profile::<slug> |
Category, requisition, location | V8.4.2 | Lab tested |
| SolarWinds NPM | Monitoring | Orion group rconfig::device_profile::<slug> |
Vendor, machine type, custom property, group, polling method | V8.4.3 | Field tested |
| Tufin AKIPS | Monitoring | None per device: instance default only | In the mlist query | V8.2.0 | Lab tested |
Field tested drivers have run against live customer environments. Lab tested drivers have run in the rConfig lab and are waiting for field results. Unverified drivers were built from the vendor’s API documentation and haven’t yet run against a live instance.
Reading the table
- Device Profile reference. Where a record has none, the instance’s Default Device Profile applies (Setup tab, V8.4.3 and later). With neither, the record is rejected and listed in Problem Devices. Infrahub and AKIPS records never carry one, so those instances need a default to create devices.
- Filters in the query. Infrahub and AKIPS have no filter form. Scope them by editing the GraphQL query or the mlist query on the instance.
- Platform editions. Observium’s API is only in its Professional and Enterprise editions, and the SolarWinds driver needs a self-hosted SolarWinds Platform server. Each driver page lists its own prerequisites.
Related reference
- Device Sync V2 overview
- Driver setup: NetBox, Nautobot, Infrahub, Zabbix, Checkmk, PRTG, Statseeker, LibreNMS, Observium, OpenNMS, SolarWinds NPM, Tufin AKIPS
- Problem Devices tab