Skip to content
Guides & References

Device Sync platforms at a glance

All twelve Device Sync V2 drivers compared: how each carries the Device Profile, filters, the release it arrived in, and test status.

IntegrationsUpdated
On this page

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

PlatformKindDevice Profile referenceFiltersFromStatus
NetBoxSource of truth Tag rconfig::device_profile::<slug> Tag, site, status V8.2.0 Field tested
NautobotSource of truth Custom field rconfig_device_profile Tag, site, status V8.2.0 Field tested
InfrahubSource of truth None per device: instance default only In the GraphQL query V8.2.0 Lab tested
ZabbixMonitoring Host tag rconfig::device_profile = slug Host groups, hosts, status, maintenance V8.2.0 Field tested
CheckmkMonitoring Host label rconfig: device_profile--<slug> Folder, label, attribute, site V8.2.0 Field tested
PRTGMonitoring Tag rconfig::device_profile::<slug> Status, tags, name V8.2.0 Lab tested
StatseekerMonitoring Group or tag rconfig::device_profile::<slug> Name, group, status V8.2.0 Field tested
LibreNMSMonitoring Device group rconfig::device_profile::<slug> Device group, OS, type, location V8.4.2 Lab tested
ObserviumMonitoring Device group rconfig::device_profile::<slug> Device group, OS, type, location V8.4.2 Unverified
OpenNMSMonitoring Surveillance category rconfig::device_profile::<slug> Category, requisition, location V8.4.2 Lab tested
SolarWinds NPMMonitoring Orion group rconfig::device_profile::<slug> Vendor, machine type, custom property, group, polling method V8.4.3 Field tested
Tufin AKIPSMonitoring 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.

Type to search.