Choosing an integration
Most integration questions come down to one of a handful of jobs. Find yours below, then follow the link. Where two features could do the job, the table says what tips the choice.
Getting devices into rConfig
| You want to | Use | Why this one |
|---|---|---|
| Keep rConfig’s inventory in step with NetBox, Nautobot or Infrahub | Device Sync | The source of truth stays the authority. New, changed and removed devices follow on the next run |
| Back up everything your monitoring platform already watches | Device Sync | Zabbix, Checkmk, PRTG, Statseeker, LibreNMS, OpenNMS, Observium, SolarWinds NPM and AKIPS have drivers |
| Pull from several Zabbix or OpenNMS servers into one rConfig | Several instances | One instance per server, each scoped by its own filters |
| Leave Oxidized, RANCID, NetMRI or SolarWinds NCM | A one-off import | The old tool is going away, so there’s nothing to stay in step with |
| Load devices from a CMDB, spreadsheet or tool with no driver | The REST API | Your code reads the source and creates devices through the API |
| Connect an ITSM, a CMDB or another NMS to a Vector deployment with a Central Manager | Central Manager integrations | Designed per deployment by rConfig Professional Services, at the Central Manager |
Device Sync or the API? If a driver exists for your platform, use Device Sync. You get preview runs, reconciliation, Problem Devices and scheduling without writing code. Reach for the API when no driver exists, or when the source of the list is your own system.
Signing people in
| You want to | Use | Why this one |
|---|---|---|
| Use your identity provider’s MFA and conditional access | SSO | Authentication happens at the identity provider, so its policies apply |
| Let identity provider groups decide rConfig roles | SAML 2.0 or Shibboleth with role mapping | The OAuth providers (Microsoft, Okta, Google) don’t map roles |
| Authenticate against Active Directory without an identity provider | LDAP | Directory sign-in with its own group to role mapping. Compared in the Security guides |
| Use the RADIUS server your network team already runs | RADIUS | Compared in the Security guides |
Device credentials
| You want to | Use | Why this one |
|---|---|---|
| Rotate device passwords without touching rConfig | A key vault | rConfig reads the current password at every connection |
| Share one set of credentials across many devices, with no vault | A device credential set | Stored once in rConfig, encrypted at rest. See device credentials |
| Keep different device groups in different vaults | Several vaults | From V8.4.2, each vault credential set belongs to its own vault |
Events out
Webhooks for config changes, failures, compliance results and agent status are covered in the API & Developer webhooks guide.