Skip to main content

Release Notes - Version 20.0

Written by Stefano Gridelli

NetBeez NextGen

NextGen is a separate product line from legacy 15.6. The two trees split on 18 September 2025. Tag v15.1.1765578170 is already on the NextGen side (338 commits past that split). Legacy then shipped 15.1 through v15.6.1794590125 (13 November 2026). These notes compare dashboard-next with that legacy tip.

NextGen replaces the React dashboard and nb-api with a Rails 8 application. Monitoring stays live on the page. Configuration is done by assigning agents, targets, scheduled tests, and Wi-Fi, with a confirmation when that change stops tests or moves an agent off a network.

It ships on the dashboard-next/production channel. A 15.x server stays on the legacy channel and will not pull this line unless that channel is changed. Legacy 15.6 also refuses version 20 and above while DISABLE_NEXTGEN_UPDATES is set.

New

Network Experience home (Buzz). The home board shows overall status, sites, online remote users, a six-way remote-user breakdown (endpoint, Wi-Fi, gateway, VPN, DNS, ISP), a geolocation map, ISP performance, target performance, Wi-Fi networks, and the last 24 hours of events. Cards update in place. Extra board layouts exist and stay hidden unless BUZZ_LAYOUT_DROPDOWN_VISIBLE is set.

Buzzy and MCP. The in-app assistant is a conversation that sees the page you are on. It can summarize, suggest what to look at on Buzz, and create or update targets, scheduled tests, ad-hoc tests, alert profiles, and monitoring conditions. Writes wait for Approve or Deny. The same tools are available to external clients at /mcp with a bot token. An administrator turns AI on under Settings. This replaces the legacy one-click summary buttons (including the 15.2 Agent Log summary).

Authenticator-app MFA. Administrators can require an authenticator app for local accounts. Turning it on signs everyone out. There are no recovery codes. SSO users, bot users, and the system user are not challenged. Administrators can reset a user’s authenticator.

Bot users. Separate token accounts for the API and MCP, with Read-only or Read-write access. They are not people and they are not asked for MFA.

License lockout. An expired license lets only administrators and support sign in, and holds them on the license screen. Bots and /mcp receive 403. Applying a license that would put an agent over its target-test cap is refused, and the product warns when an agent reaches that cap.

In-product updates, health, and migration. Administrators schedule or install an update from Information & Health. Everyone sees a pending update on the nav clock. The same area shows maintenance mode, load, and disk. A migration panel shows legacy cutover progress, a remaining-time estimate, and a downloadable error report.

Events workspace. The old Alerts destination is Events: alert opens and closes, incident events, and agent events, as a table or a split view with the test graph. Filters, a brush, and an Overlays menu (alerts, runs, CPU, memory) sit on the same time axis. Incidents stay on the agent, target, and Wi-Fi profile. They are not a separate top-level app.

Live investigation graphs. Test graphs scroll on a shared clock, show a live dot, brush to a range, and zoom by dragging. Jitter, MOS, and packet loss are calculated onto ping graphs.

Interactive console. The agent console opens in the page, sized to the viewport, or in its own window. Who may open it is a setting.

SSID scan workflow. Scan results can be searched, given custom columns, and exported to CSV. Channel utilization is shown, and Create Profile prefills security from the scan.

Reports rebuilt. A wizard builds line, area, column, pie, and table charts over agents, targets, scheduled tests, and Wi-Fi. Schedules can be paused, resumed, and cloned. System schedules generate a Network Summary and an Agent report. Public viewing is a setting. A finished report exports to PDF.

Notification contacts. Target notification addresses are stored as contacts, and the form suggests addresses you have used before.

First-run onboarding. A new server walks through SaaS targets, target templates, inviting the team, and remote workers. Invitation email is sent from the product.

Rebuilt

These legacy jobs exist again in NextGen, with a different workflow.

  • Navigation. Buzz, Network Agents, Remote Workers, Targets, Wi-Fi, Scheduled Tests, Ad-Hoc Tests (only if you can create them), Reports, Events, Buzzy, Settings, Account, and Help & Support. The last entity you opened is remembered. Lists are tables or thumbnails, with skeletons, custom columns, and search. Agent lists filter by group, software version, country or region, and network-experience category.

  • Roles. Read-only, Read-write, Administrator, and None apply to screens, APIs, and live updates. Read-only users do not see Ad-Hoc Tests. SSO can map a default role.

  • Account. Profile, password, active sessions (list and revoke), preferences, and an inbox for license, SSO, maintenance, and settings notices.

  • SSO. Microsoft Entra ID and SAML remain. The product warns, in the app and by email, as those credentials near expiration.

  • Agents. Register, install, invite remote workers, activate or deactivate, reboot a network agent, pause or resume all tests, and blacklist. Tabs are Monitoring, Event Log, Path Analysis, Scheduled Tests, plus Wi-Fi and Console when they apply.

  • Assignments. Agent groups, targets, scheduled tests, Wi-Fi profiles, and hopping groups are managed together. The confirmation explains when the change stops tests or moves Wi-Fi. Group membership creates the concrete tests. One-to-one scheduled tests stay out of the group wizard.

  • Targets. Custom, SaaS catalog, and templates (DNS, gateway, VPN, website) for Ping, DNS, HTTP, Traceroute, and Path Analysis. Associating an agent or group creates the running tests. Wizards can save on every step. Pause and resume covers the target, including path analysis and traceroute.

  • Scheduled tests. Iperf, Network Speed, VoIP, Packet Capture, and Custom Command, on a cron, run in parallel, serial, or at random inside a time window. Run Now, live results, and a per-agent breakdown are in the product. Orchestration (locks, destination before sources, parallel/serial/random) runs in NextGen.

  • Ad-hoc tests. Ping, DNS, HTTP, Traceroute, Iperf, Network Speed, VoIP, Packet Capture, and Custom Command. Runs stay on that user’s page. Packet captures show progress and download a .pcap.

  • Wi-Fi. Profiles and hopping groups have their own wizards, monitoring, access points, timing, and event log. Deleting a profile that is still in a hopping group is blocked. Reassignment asks first.

  • Path analysis. Agent and target route graphs follow the selected test, interface, and Wi-Fi profile.

  • Alerts and incidents. Alert profiles and monitoring conditions are in Settings. Detection covers target-test metrics (ping, DNS, HTTP), scheduled tests, unreachable agents, and Wi-Fi connectivity. Incidents correlate failing tests for an agent, target, or Wi-Fi profile.

  • Integrations. SMTP, Slack, Microsoft Teams, PagerDuty, ServiceNow, Splunk, syslog, SNMP, and webhooks, each with a connectivity check that does not require saving first. Delivery of alerts and incidents is implemented on those channels. Intercom is the Help & Support launcher.

  • Data retention. Retention settings drive TimescaleDB policies for metrics, hop results, events, and logs, plus report retention and cleanup of unreachable remote workers.

Legacy 15.2–15.6, carried into NextGen

These shipped on the legacy line after the split. NextGen has its own implementation.

Legacy change

In NextGen

Wired scheduled tests on Wi-Fi agents, including destination IP for that interface

Yes

Ad-hoc wired or wireless interface selection

Yes. Packet capture has no interface picker, matching the 15.4 removal

Ad-hoc custom command (bash or Python, timeout, output schema)

Yes

IPv4-only and skip-IPv6 for ping and DNS

Yes

DNS record types A, AAAA, PTR, CNAME, TXT, MX, NS, CAA, SRV

Yes

Cellular interface on remote workers

Yes, display only. It is not configurable

Invite remote workers from the dashboard

Yes

ServiceNow events include failing destinations

Yes, up to 20

Scheduled-test alerts on webhooks, and aggregation_entity_type on aggregate payloads

Yes

Webhook and ServiceNow timeouts (5s open, 10s read)

Yes

Alert mode recalculated when a detector is removed

Yes

Wi-Fi profile name sent to the agent

Yes

PING and DNS labels so similar tests can be told apart

Yes

Collapsible scheduled-test details

Yes

Path analysis historical range selection

Yes, with a brush and timeframe selector

Inverted ping Don’t Fragment packet-size ranges

Yes

Wi-Fi interface updates no longer dropped because of server time

Yes. NextGen uses the event time

SSH port read from sshd_config ignores comments

Yes

Password reset when a security question is missing

The reset flow is token and new password. Security questions are gone

Removed or not carried forward

Authentication

  • LDAP is not implemented. Migrated LDAP users become local users and must reset their password.

  • Security questions are dropped.

  • JWT API sessions are dropped.

API and identity

  • Integer ids become UUIDs. Legacy API ids do not round-trip.

  • The legacy v0, v1, and unversioned nb-api routes are not served. NextGen is the Rails app plus JSON:API.

  • Bearer API keys become bot users. Clients send Authorization: Token token=<secret>, email=<bot-email>. Read-only and read-write keys keep those roles. They do not become administrators.

  • Encrypted settings are re-encrypted with keys from Vault. Old ciphertext cannot be copied across.

Alerts

  • Traceroute alert detectors are not migrated (unsupported_traceroute_alert_detector). Traceroute and path analysis still run. They do not take alert detectors. Ping, DNS, and HTTP do.

  • Percentile-mean alert conditions are not migrated. Percentile statistics themselves are computed by default, so the old percentile setting is dropped.

  • Custom JavaScript error-code windows, and blank or hand-edited conditions that do not match a known detector, are not migrated.

  • Agent-up and Wi-Fi connectivity detectors are replaced by seeded rules, not copied line for line.

Data left behind

  • Previously generated reports, schedules, and presets are not copied. NextGen starts with its own report schedules.

  • Historical agent logs are not copied. New logs are stored and shown in Wi-Fi Timing and the event log.

  • Old pre-aggregated statistics are not copied. Graphs use Timescale continuous aggregates.

  • Annotations and tags are not copied.

  • Samples older than the legacy retention window are not copied.

  • The remote-support setting is dropped. The built-in agent console remains.

Product analytics

  • Pendo tracking from the React dashboard is not in NextGen. Intercom remains the support launcher.

Platform

Legacy 15.6

NextGen

UI

React dashboard

Rails, ViewComponent, Hotwire

API and jobs

nb-api, Sidekiq, Redis

Rails 8, Solid Queue

Database

MySQL and InfluxDB

PostgreSQL and TimescaleDB

Agent messaging

Redis queues

Kafka (1, 3, or 5 brokers)

Console

msgsrv

ActionCable and NATS

Secrets

Environment and Rails secrets

Vault

PDF

wkhtmltopdf service

Generated in the app

Updates

Legacy production channel and update containers

dashboard-next/production, host installer, in-product schedule

Agents do not all have to be upgraded first. Agents on major version 19 and below still connect. MySQL and InfluxDB run only during migration, and each verified source is then dropped. Rollback is a VM snapshot taken before cutover.

Still different from 15.6

These are real gaps, not a different design on purpose.

  • Path analysis interval minimum is still 60 seconds. Legacy 15.5 allows 1–3600 seconds and warns under 60, for low-TTL tests.

  • Path analysis hop RTT in the NextGen graph is still truncated to whole milliseconds. Legacy 15.3 keeps three decimal places.

  • Registration stores kernel_version only. Legacy 15.4 also folds in kernel_release.

  • Ad-hoc HTTP does not prefix https:// when the destination has no scheme. The target wizard does.

  • Path analysis tests are labeled by target and interface or Wi-Fi profile, not by SSID.

  • Incident views do not default the filter to Open the way the 15.1 timeline widgets did.

Light and dark themes are a proof of concept and are not part of this release.

Did this answer your question?