rConfigobservium.org ↗
rConfigPair Observium with rConfig.
rConfig reads your Observium device list over the REST API and backs up, diffs and checks every device's configuration.
For Observium Professional and Enterprise. Read-only: nothing is written back to Observium.
Preview driver, in rConfig V8.4.2.
Preview. The Observium driver ships in rConfig V8.4.2 and was built from Observium’s published API documentation. It has not yet been tested against a live Observium installation. If you run Observium Professional or Enterprise, we’d like to test it with you.
Observium knows every device. rConfig keeps their configs.
Observium knows every device and graphs every port. It doesn’t keep a versioned, searchable history of their configs with compliance checks.
For Observium network configuration management, rConfig reads the device list Observium already holds, so there is no second inventory to maintain. Every configuration lands in a versioned archive from the first sync.
The API is only in Observium’s Professional and Enterprise editions. Community Edition is not supported.
Sync, capture, prove.
Three moves take an Observium inventory to backed up, checked and audit ready.
Sync
rConfig reads the device list from Observium and keeps it in step on a schedule. Each device gets its template, credentials and category from an Observium device group.
Capture
Scheduled backups of every synced device, stored and diffable. Every change is kept as a version you can compare and restore.
Prove
Compliance policies run against every synced device. Audit evidence exports from the same place.
How rConfig syncs with Observium.
Four steps, from turning on the API to a scheduled sync.
Authorise
Turn on the API in Observium’sconfig.php, then create a read-only API token (newer builds) or use a username and password (older builds). Use user level 5 (global read) or higher.Map
Create Observium device groups namedrconfig::device_profile::<profile>. Each group maps its devices to one rConfig profile.Scope
Optionally filter by device group, OS, device type or location. Disabled devices are skipped by default.Sync
Preview, run, then schedule. From the CLI, runphp artisan rconfig:integration-v2-run --driver=observium.
Built for Observium users.
The jobs the NOC, the security team and the auditor each need from network configuration management.
Multi vendor configuration backup
Cisco, Juniper, Arista, Fortinet, Palo Alto, Huawei, Nokia, MikroTik, HPE, Aruba and 200 more. Hourly, daily or on demand.
Change detection with a readable diff
See exactly what changed, line by line, since the last known good version. Filter out noise like timestamps and session identifiers.
NIS2, DORA and CIS compliance reporting
Write policies once, run them against every Observium device. Export evidence your auditor can actually read.
One click configuration restore
Push a known good configuration back to any device, with approvals and a full audit trail.
Bulk configuration deployment
Apply the same template across every Observium device that matches a filter, in a single job with preview and rollback.
Full audit trail, exportable on demand
Who changed what, when, from where. Export the report your auditor asks for.
Deploys alongside Observium.
rConfig and Oxidized, next to Observium.
Oxidized is free and works well for plain config backup. rConfig adds scheduled compliance checks, diffs and restore in a UI, RBAC and an audit trail, with the device list synced from Observium.
The Observium integration, at a glance.
- rConfig version
- V8.4.2 and later
- Status
- Preview: built from the API documentation, not yet tested against a live instance
- Observium editions
- Professional and Enterprise (API required). Community Edition not supported. See observium.org for editions.
- Authentication
- Read-only API token (Bearer), or username and password
- Transport
- HTTPS REST, read-only, paged
- Device profiles
- From Observium device groups named
rconfig::device_profile::<slug> - Filters
- Device group, OS, device type, location
- Disabled devices
- Skipped by default; optional
- CLI
php artisan rconfig:integration-v2-run --driver=observium- Write-back
- None
- Documentation
- Observium driver docs, Device Sync V2 overview
Observium config backup: common questions
What Observium subscribers ask about the preview driver. If yours isn't here, ask it on a call.
Does it work with Observium Community Edition?
No. Community Edition has no API.
Has it been tested?
Not yet against a live Observium. It was built from Observium's API documentation and is covered by automated tests built from that documentation. We're looking for subscribers to validate it with.
Which sign-in does it use?
A read-only API token where your build has them; otherwise a username and password.
Can rConfig do Observium config backup?
rConfig reads the device list from the Observium API and backs up each device's configuration itself, with diffs, compliance checks and restore. Observium Professional or Enterprise is required for the API.
Does rConfig write back to Observium?
No.
What happens when a device is removed from Observium?
By default rConfig unlinks it and keeps the device and its backup history.
Run Observium? Help us validate the driver.
The Observium driver is a preview. Book a call and we'll test it against your Observium Professional or Enterprise installation with you.