rConfigSync your Statseeker inventory. Back up every config. Prove it to your auditor.
rConfig V8.2.0 reads your Statseeker host list directly over the REST API, backs up the running configuration of every one of those devices on the schedule you choose, tracks every change line by line, and generates the NIS2 or DORA evidence your compliance team needs, without CSV exports, without custom scripts, without a second inventory to keep alive.
Group-scoped sync200+ vendorsNIS2 and DORA reporting
Statseeker answers whether the network is up. It never answered what’s on it.
If you run Statseeker, you already know what it’s good for. Sixty-second polling. Long-memory historical data. Root-cause investigations that actually finish. It’s why it sits on the NOC’s primary screen.
Now try asking Statseeker three awkward questions. What was on that core switch the day before it failed. Who added the inbound ACL at 02:14 last Tuesday. Can we push the last known-good firewall config back in under two minutes if this morning’s change turns out to be the reason the VPN is dead.
None of those are monitoring questions. They’re configuration management questions, and they’ve been living in a gap between Statseeker and whatever scripts, spreadsheets or open-source tools your team has bolted on to fill it.
- Device running-configs aren't in Statseeker. They never were.
- Home-grown scripts using SNMP writes and TFTP break the week you need them most.
- Oxidized works until the engineer who maintained it leaves.
- Auditors don't care that your ACL was reachable. They care what it looked like every Friday for the last twelve months.
rConfig V8.2.0 closes that gap, and it does it without asking you to rip out a single thing.
Partner baselineNetwork intelligence means answers, not excuses.
Before we talk about configuration, credit where it is due. This is why Statseeker sits where it sits, and why rConfig is the complement, not a competitor. Read the full picture on the official Statseeker site.
Detect faster
60-second polling at scale. Proactive fault detection across the whole estate. Short-lived issues that averaged data would hide, surfaced while they are still happening.
Prove root cause
Granular historical data, kept at full resolution. The ability to ask what the network actually looked like at 02:14 last Tuesday, and get an answer, not an estimate.
Prevent recurrence
Predictable patterns, predictable alerting, predictable capacity signals. A platform engineers trust enough to sit on the NOC's primary screen.
Detect · Prove · Prevent
Built for how NetOps teams actually work
The capabilities Statseeker teams pick it for, lifted from the product page so you can recognise the shape of your own environment.
High-scale polling engine
Monitor up to 50,000 devices on a single server, every 60 seconds, without the performance penalty most monitoring stacks ship with.
Dashboards that lead to answers
Operator-friendly views wired straight to the underlying data, built for engineers under pressure.
Actionable alerting
Thresholds and anomaly rules engineered to cut through noise. Fewer pages, higher signal.
Traffic and flow visibility
NetFlow and sFlow context next to the interface graph. Who is using the link, not just whether it is saturated.
Accurate inventory and MAC / IP history
A fleet list that stays current. MAC and IP history you can trust when the question gets asked six weeks later.
Powerful monitoring on a single server. Works on day one. Remains reliable for years. That is the Statseeker promise, and rConfig is built to stand beside it, not replace it.
Configuration intelligence, in three moves.
Three capabilities that turn a monitored estate into an audit-ready one. Every Statseeker device, captured, diffable, and defensible.
Sync
Statseeker hosts become rConfig devices automatically, scoped by Statseeker group. Add a device upstream, it lands in rConfig on the next schedule.Capture
Every running-config, every startup-config, every change, stored and diffable. 200+ vendors out of the box. No Jinja. No Python. No vendor plugin to maintain.Prove
Compliance policies run against every Statseeker-managed device. NIS2, DORA, PCI-DSS, CIS benchmarks and anything your security team writes. Evidence exports in minutes.
Statseeker watches. rConfig remembers. Together, they’re the answer to every awkward question your auditor has ever asked.
How rConfig syncs with Statseeker, step by step
Four screens. Ten minutes for a test group. Group-based mapping that scales cleanly from a pilot to the whole estate.
- 01Step 1: AuthoriseDrop a Statseeker REST API token and URL into rConfig's Integrations screen. The Test Connection and Test Credentials buttons confirm reachability in seconds.
- 02Step 2: ScopePick which Statseeker hosts to bring across. Scope the sync by Statseeker group. Most teams start with a test group of five to ten devices and widen from there.
- 03Step 3: MapTranslate each Statseeker group into rConfig vendors, templates and credentials using group-based mapping. Set it up once, rConfig applies it on every sync thereafter.
- 04Step 4: SyncRun it now, schedule it (hourly, daily, weekly), or trigger it from the CLI with
php artisan rconfig:integration-statseeker. Idempotent: re-runs produce identical state, failures resume cleanly on the next cycle.
Once the sync lands, rConfig takes over. Daily backups against your multi-vendor estate. Diffs that filter out timestamps and AAA session noise. Policy-driven compliance reports. One-click restore. Nothing else to wire up.
Built for how Statseeker teams actually work
The jobs the NOC, the security team and the auditor each need from configuration management. Nothing bolted on for show.
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 Statseeker-managed device. Export evidence your auditor can actually read.One-click configuration restore
Push a known-good configuration back to any device in under 90 seconds, with approvals and a full audit trail.Bulk configuration deployment
Apply the same template across every Statseeker host that matches a filter, in a single job with preview and rollback.Full audit trail, exportable on demand
Who changed what, when, from where. The report your auditor asks for takes minutes, not days.
Deploys alongside Statseeker. Stays in its lane.
rConfig doesn’t replace Statseeker. It doesn’t try to. It doesn’t poll interfaces, it doesn’t graph throughput, it doesn’t do anomaly detection on link errors. That’s Statseeker’s job, and Statseeker does it better than anything else in the category.
What rConfig does is the thing Statseeker was never built for: capturing configuration, tracking how it changes, and proving what it looked like when an auditor asks. Self-hosted if you need it, VM or bare metal, on-prem or in your private cloud. Vendor-agnostic. Multi-tenant capable. Your ops team is running it inside 30 minutes on V8 Pro or Vector.
Your monitoring.Your configuration.Your audit trail.
From Statseeker alert to restored configuration, in under ten minutes.
A regional service provider runs Statseeker across roughly 6,000 devices spread between core sites in Dublin, Manchester and Frankfurt. At 03:12 on a Tuesday, Statseeker pages the on-call engineer about a core switch in Frankfurt. By the time the engineer has joined the bridge and pulled the last six hours of interface data from Statseeker, rConfig has already surfaced the configuration change that caused it (a misapplied QoS template pushed by a contractor two days earlier) and offered the engineer a one-click rollback to the known-good version from the previous Friday. Restoration completes at 03:22. The post-incident report writes itself.
That’s the difference between telling the board the switch was down for an hour and showing them it was back in ten minutes.
NIS2 and DORA evidence, sourced from the network you’re already monitoring.
If you’re in scope for NIS2 or DORA, the regulators want two different things. They want to know the network was available, and they want to know it was configured correctly. Statseeker is excellent evidence for the first half. rConfig is the evidence for the second.
Run both and your compliance team stops asking the NOC for screenshots at 4pm on a Friday. Policy checks run automatically, every day, against every device Statseeker knows about. When the auditor asks, the report is already waiting.
rConfig compared to Oxidized, RANCID or a home-grown config backup script
Oxidized and RANCID are fine tools for teams with a dedicated automation engineer, a tolerance for YAML and Git debugging, and a small enough estate that maintenance isn’t a full-time job. They’re free. Free is often the point.
What they don’t give you: a web UI your NOC can operate on day one, pre-built multi-vendor compliance policies, commercial support with SLAs, RBAC, SAML SSO, approval workflows, and NIS2 or DORA reporting that doesn’t need a Python developer to generate.
Most teams move to rConfig after they outgrow the operational cost of the open-source path. If your audit exposure has caught up with you, or if you’re one departure away from losing the only engineer who understood how the Oxidized stack was held together, that’s usually the tipping point. The Statseeker integration in V8.2.0 removes the last reason to delay. Other source-of-truth integrations like the Zabbix connector follow the same pattern if your stack extends further.
The Statseeker integration, at a glance
Everything your architecture review will ask about. Share this page with your security team before the demo.
- rConfig version
- 8.2.0 or later (V8 Pro, Enterprise or Vector)
- Statseeker versions
- v5.6.0 and all v25.x releases
- Authentication
- Statseeker REST API token
- Transport
- HTTPS, with optional support for internally-signed certificates
- Sync triggers
- Manual, scheduled, or CLI
- CLI command
php artisan rconfig:integration-statseeker- Single-device CLI
php artisan rconfig:integration-statseeker-single-device {host_id}- Data flow
- One-way, Statseeker to rConfig
- Idempotency
- Yes, re-runs produce identical state
- Logging
- Every sync logged with user, timestamp, host count, errors
- Deployment
- On-prem, VM, or your private cloud
- High Availability
- Supported (point rConfig at the Statseeker HA virtual IP)
- Documentation
- docs.rconfig.com/integrations/device-sync-overview
Questions Statseeker users ask about network configuration management
See the sync running against your own Statseeker inventory.
Book 30 minutes with an rConfig engineer. We’ll point the integration at a slice of your real Statseeker estate, back up a handful of your own devices, and run a compliance report against a policy that matters to your team. No generic demo. No slide deck. No sales gate.
No slide deck. No generic demo. No waiting for the second sales call to see the product.