rConfig v8.2.0: New Device Integrations, Custom Dashboards & a Live Debug Console

rConfig v8.2.0 is officially out, and honestly, this one has been a labour of love. It's a big release, packed with features we've been asked for, features we've wanted to ship for a while, and a handful of quality-of-life improvements that make day-to-day work in rConfig just nicer.

If you only skim the highlights, here's what matters most:

• A brand new customisable dashboard with draggable, resizable cards
• A refreshed device sync engine with first-class support for CheckMK, PRTG, Infrahub, Tufin AKIPS and Statseeker
• A Live Debug Console for in-browser device troubleshooting
• Microsoft Teams notifications
• Vector agent side-load for air-gapped and locked-down environments
• Several new REST API v2 endpoints
• Token-aware XFTP rule matching

There's plenty more shipping with 8.2.0, and for the full changelog you'll find everything over on the rConfig changelog page. But this post walks through the headline additions that most teams will feel day one.

A Dashboard That's Actually Yours

Let's start with the one you're going to see the second you log in. The rConfig dashboard is now fully customisable. Cards are draggable, resizable, and re-orderable, and your layout is saved per user, not per install. So if you want a wall of compliance cards and nothing else, you can have it. If you want latest errors front and centre, drag them there.

Under the hood we're using grid-layout-plus, which gives us a proper grid with responsive rebalancing across breakpoints rather than a freeform absolute-position mess. And crucially, your layout lives in a proper relational table (user_dashboard_layouts), not a JSON blob stuffed into the users table. That matters when we need to query or migrate those layouts later, or extend them with shared team dashboards further down the line.

We've also expanded the card catalogue. New cards include latest added devices, latest error devices, latest down agents, latest checked-in agents, and latest compliance reports. The dashboard should finally feel like a proper operations surface rather than a one-size-fits-nobody landing page.

New v2 Device Sync Integrations

This is the big one for ops teams running rConfig alongside their monitoring or source-of-truth stack. We've done a major refresh of the device sync engine, and the list of supported integrations has grown meaningfully.

Newly supported integrations in v8.2.0:

• CheckMK: Pull your monitored hosts directly into rConfig as managed devices.
• PRTG: Same story for PRTG shops, with device and group metadata carried across.
• Infrahub: For teams adopting Infrahub as a source of truth, rConfig now speaks to it natively.
• Tufin AKIPS: Customer-driven addition, specifically asked for by teams running AKIPS in large enterprise environments.
• Statseeker: Added for import scenarios where Statseeker owns the device catalogue.

Refreshed integrations:

• Zabbix has been substantially reworked, and now supports both legacy username/password auth and modern API token authentication, which a lot of larger Zabbix shops have been moving to by default.
• NetBox has been refactored alongside the new device profile feature, and a long-standing pagination issue on larger extracts has been resolved.

If you're currently using the older Zabbix or NetBox integration, don't panic. We've moved the existing flows to a clean legacy path so your current syncs keep working unchanged. You roll forward to the new integration when you're ready, not when we say so.

For anyone thinking about vendor lock-in or fragile integrations, this is the release where rConfig's place in a modern network stack gets a lot easier to defend. You can point it at CheckMK, NetBox, Zabbix, Infrahub, PRTG, AKIPS or Statseeker and it just works, without writing a scraper.

Live Debug Console

If you've ever had to SSH into a customer's rConfig box to diagnose why a specific device isn't downloading its config, the Live Debug Console is for you.

It's a fully in-browser debug flow. You pick a device, kick off a debug run, and live output streams back to your browser over SSE (with a graceful polling fallback for proxied or locked-down environments). The run is queue-backed on the server side, so it doesn't block your web request, and there's a proper 5-minute timeout and status tracking across the whole lifecycle.

The real kicker is the analysis engine. Instead of dumping raw SSH output at you and wishing you luck, rConfig now interprets the most common failure patterns:

• Auth and connectivity issues ("No config data returned", etc.), with a recommendation to validate via rConfig CLI, check firewall and port state, and verify credential case sensitivity
• Prompt timeout near-misses, where the template timeout is within 1 second of the device's last response, a near-certain prompt mismatch
• High-latency warnings when response times creep above 3 seconds

Priority matters here: if a higher-priority rule matches, we stop evaluating lower-priority ones. You get the one thing that's most likely wrong, not a wall of maybes.

Microsoft Teams Notifications

Long overdue, and very much requested. rConfig notifications can now go to Microsoft Teams alongside the existing Slack and email channels.

The setup is the same pattern as Slack: configure an incoming webhook on your Teams channel, paste it into rConfig, and your compliance alerts, task failures and backup status updates land where your NetOps team actually lives. If your org standardised on Teams two years ago and has been copy-pasting rConfig alerts manually ever since, that ends today.

Vector Agent Side-Load

Vector is rConfig's distributed agent for large-scale, segmented and edge deployments, and one consistent pain point has been the first-install experience in environments that can't reach out to fetch binaries.

v8.2.0 adds a proper Vector binary side-load command and accompanying UI. You upload the Vector binary to your rConfig server, point the agent installer at it, and it deploys without any outbound internet access required. For anyone running rConfig in a secure or air-gapped environment, or anywhere with strict egress controls, this removes a big blocker.

We've also cleaned up the Vector table UI, fixed some SSL verification handling bugs across agent settings, and improved the overall agent management experience. Not headline features, but the kind of changes you'll notice when you're actually in there deploying agents.

New REST API v2 Endpoints

The API surface has grown in 8.2.0, and it's also been aligned more tightly with what's actually implemented (the API docs and the codebase now agree with each other, which is embarrassing to have to say, but important).

New and updated endpoints include:

• Compliance logs v2: Programmatic access to compliance run results
• Dashboard health-latest: Single endpoint for the dashboard health status card, useful for external monitoring
• Devices v2: Pagination enhancements, per_page/perPage parity with a safe cap, and new top-level last_backup_status and last_backup_at fields directly on list responses
• Devices summary: Lightweight summary endpoint aimed at monitoring integrations
• Parameterised snippet deployment: You can now send parameters with snippets via the API, which a few customers have been asking for

If you're building integrations against rConfig, the contract is finally stable enough to treat it as production.

Token-Aware XFTP Rule Matching

XFTP rules got a targeted but genuinely useful upgrade. We've added explicit dual-mode token syntax for filename matching:

• {pattern.*} tokens let you describe patterns in the rule itself
• {current.*} tokens resolve against the file being evaluated

Matching is case-sensitive by default, and the new compilation logic safely isolates parsing from the larger sweep command, so a malformed rule can't take down the batch. Backward compatibility is fully preserved, no schema changes, and there's test coverage across matching, API validation, authorization and DB side effects.

If you use XFTP for config file intake from third-party systems and you've been fighting timestamp-based filenames, this one's for you.

One More Thing: rconfig-sim

Slightly off the release itself, but worth mentioning here because a lot of you asked for it. Alongside v8.2.0 we've also open-sourced rconfig-sim, our network device simulator for NMS and config management load testing.

The pitch is simple: stand up 50,000 simulated Cisco IOS devices on a single Linux host. Real SSH, realistic running-configs, and zero-copy delivery, all built specifically for stress-testing network configuration management tooling at scale.

We built it internally to benchmark rConfig against 100k-device workloads, and it was too useful to keep to ourselves. If you're sizing a deployment, testing integrations, validating agent throughput, or just curious whether your NMS can actually handle what the sales team claims it can, point rconfig-sim at it and find out. It's free, it's open source, and it'll happily burn through whatever tinfoil-grade performance numbers your incumbent vendor quoted you last quarter.

More details, installation instructions and the repo link are over at rconfig.com/rconfig-sim.

And Much More

I've only covered the headlines here. v8.2.0 also ships with:

• An RBAC Editor upgrade with in-panel role-to-user mapping
• Compliance exports in PDF, HTML, CSV and JSON
• A rebuilt Config Search with multiselect filters and AND/OR multi-term logic
• Contextual settings navigation
• SAML2, Shibboleth and Sanctum authentication hardening
• A performance fix for bulk device delete on large installs
• And a healthy list of bug fixes and UX polish

The full breakdown, as always, is on the rConfig changelog page.

Upgrading

v8.2.0 is available now for all rConfig and rConfig Pro customers. Follow the standard upgrade path from the docs, and as always, if you run into anything odd, open a ticket in the customer portal and we'll take a look.

Thanks to everyone who raised feature requests, logged bugs, or just sent a quick note about what was and wasn't working in 8.1.x. This release is a direct response to that feedback, and we'd love to hear what you think once you've had a few days with it.

Happy configging.