Browse, vote, and track the status of feature requests from the NetBrain community
Browse open ideas available for voting, feedback, and discussion.
View ideas that are planned for future product development.
Explore ideas that are currently being developed by the product team.
Explore ideas that are now available in the product.
View ideas that are not currently planned for product development.
NetBrain currently discovers all devices within a connected Meraki network, with no option to limit discovery to devices matching specific tags. This enhancement would allow administrators to define tag-based criteria so that only Meraki devices with matching tags are discovered, rather than the entire network. Customers managing large or segmented Meraki environments would benefit from more targeted discovery, reducing unnecessary device volume and simplifying ongoing network management.
Dashboards currently use a fixed widget layout, so users cannot reposition or resize individual widgets to fit their preferred view or screen size. This enhancement would allow widgets to be freely moved and resized within the dashboard canvas. Customers building operational or executive views would gain more control over how information is arranged and prioritized on screen, improving usability for teams with varying monitoring needs.
NetBrain currently requires users to manually run the 'analyze relevance' and 'generate assets' steps within the Golden Assessment Library each time a new device needs to be evaluated against golden assessment rules. This enhancement would introduce automated detection of newly discovered devices along with an automatic trigger of the relevance analysis and asset generation process, eliminating the need for manual intervention. Customers managing large or dynamic environments would benefit from consistent, up-to-date assessment coverage as new devices are added, reducing administrative overhead and the risk of gaps in compliance monitoring.
NetBrain currently allows an Automated Data Table to be populated using the inbuilt ARP table filtered by a device group, with an auto-rebuild option intended to keep the table current. However, when this configuration is used, the auto-rebuild process does not consistently refresh the table with the latest ARP data, leaving stale entries in place. This enhancement would ensure that ADTs built from the inbuilt ARP table and a device group are reliably refreshed on each auto-rebuild cycle, so the data reflects the most recent poll results. Customers using such ADTs to detect duplicate IP addresses across their network would gain accurate, up-to-date results without needing to manually rebuild the table or verify data currency through other means.
NetBrain currently calculates the CLI access rate based on how a device type or driver is configured, without accounting for the method used to discover the device. As a result, devices that were intentionally discovered via SNMP-only are still counted against the CLI access rate, even though CLI access was never expected or intended for those devices. This enhancement would update the CLI access rate calculation to take discovery method into account, excluding devices discovered via SNMP-only from the CLI access rate metric. Customers who rely on the CLI access rate as an indicator of platform value would benefit from a more accurate representation of true CLI coverage across their environment, avoiding metrics skewed by devices that were never intended to be CLI-accessible.
NetBrain currently requires users to manually enable the 'Hide value and disable editing for others' option on each change template individually, with no way to configure it as a default at the template level. This enhancement would allow administrators to set this option as a default behavior for a given change template, so it applies automatically without repeated manual configuration. This would reduce administrative overhead and help ensure consistent visibility and editing restrictions are applied across teams using the same template.
NetBrain currently does not provide a way to visually distinguish unknown end systems on maps based on their status. This enhancement would allow unknown end systems to be highlighted or color-coded according to their status, similar to how recognized devices can be visually flagged. Customers troubleshooting networks with a high volume of unknown end systems would benefit from faster visual identification of systems requiring attention, reducing time spent manually inspecting each entry.
NetBrain currently does not provide an API to trigger execution of all paths that have already been pre-configured within an application. As a result, external systems, such as an ITSM platform responding to an application incident, cannot programmatically initiate a full path run for that application without manual intervention in the user interface. This enhancement would introduce an API endpoint that, when invoked, executes all pre-configured paths associated with a given application. Customers integrating NetBrain with incident management systems would benefit from automated, on-demand path execution triggered directly by an application-related incident, reducing manual steps and accelerating root-cause investigation.
NetBrain's AI-powered features currently integrate only with OpenAI as the underlying AI provider, with no option to connect to alternative AI services such as Microsoft Copilot. This enhancement would add configuration support for Microsoft Copilot as an alternative AI engine within NetBrain. Customers already standardized on Microsoft Copilot within their organization would benefit from leveraging existing AI investments and maintaining consistency with their preferred AI ecosystem.
NetBrain currently enforces a fixed CLI timeout of 5 minutes in Device Settings, which causes long-running commands, such as 'show tech-support' on certain platforms, to fail before completion. This enhancement would allow administrators to configure or extend the CLI timeout value for command execution beyond the current default, independent of other module-specific timeout controls. Customers running commands that require extended execution windows would benefit from reduced task failures and more reliable diagnostic data collection.
NetBrain path trace currently stops abruptly when it encounters a next-hop device that has not been modeled in the system, whether the trace is running live or against cached data. This forces users to manually model the device before the trace can continue, interrupting the troubleshooting workflow. This enhancement would allow the path trace engine to automatically attempt discovery of an unmodeled next-hop device by logging in with available credentials, identifying its platform and software version, and applying the appropriate driver to continue the trace without manual intervention. Customers troubleshooting paths that cross undocumented or newly added devices would gain uninterrupted end-to-end path visibility, reducing the manual effort required to keep the network model current.
NetBrain currently does not provide a unified launch page where users can view and access their automation assets, such as Chat Bot, Auto Intent, and Automated Data Tables, from a single location. Users must navigate separately to each automation type to locate and run the assets they need. This enhancement would introduce a customizable launch page that consolidates these automation assets into one configurable entry point. Customers would benefit from faster access to frequently used automation tools and a more streamlined, personalized experience when managing their automation workflows.
NetBrain Change Management currently does not support pushing configuration changes to Cisco SD-WAN devices through their management API, requiring customers to rely on manual, out-of-band processes for these devices. This enhancement would extend Change Management to integrate with the Cisco SD-WAN API, enabling configuration changes to be pushed and tracked in the same manner as other supported device platforms. Customers managing Cisco SD-WAN environments would benefit from consistent, automated change workflows and reduced manual effort in maintaining device configurations.
The InterfaceByIP function in Network Intent currently returns interface information without any indication of VRF membership, even when the resolved interface belongs to a non-default VRF. This enhancement would extend the function's output object to include a VRF attribute alongside the existing interface data. Customers building automated remediation logic, such as setting a source interface for services like NTP, would be able to correctly account for VRF context without requiring a separate lookup step.
NetBrain currently does not allow any user to log in once the concurrent user seat license limit has been reached, regardless of that user's privilege level or operational priority. There is no mechanism for a higher-privilege user to gain access by displacing an active session held by a lower-privilege user. This enhancement would introduce a configurable privilege that permits designated users to log in even after the seat limit is reached, automatically ending the session of an active user who does not hold the same elevated privilege. Customers with critical personnel who require guaranteed access during peak usage periods would benefit from reduced operational disruption caused by license contention.
NetBrain currently does not provide clear validation or diagnostic feedback when an SCM manager path is misconfigured or unavailable during Ansible task setup, leaving users with a generic path-not-available error and limited guidance on resolution. This enhancement would introduce improved validation checks and descriptive error messaging for SCM manager path configuration, helping users identify and correct drive or path accessibility issues before task execution. Clearer diagnostics would reduce setup time and support effort for customers configuring Ansible-based automation within NetBrain.
Today, when a triggered diagnosis is initiated through an API-driven trigger to generate a map for an incident, the diagnosis executes against all devices present on the resulting map rather than being limited to the specific device under investigation. This enhancement would scope triggered diagnosis execution so it runs only against the intended target device identified by the incident trigger, regardless of how many other devices appear on the generated map. Limiting execution to the relevant device would reduce unnecessary diagnostic load on unrelated devices and help ensure that diagnostic results remain focused and accurate for the reported issue.
NetBrain currently does not provide a way to export a diagnosis report after running Auto-Intent on a map; diagnosis notes and results are only viewable within the map interface itself. This enhancement would add an export option, such as PDF or CSV, that allows users to generate a report of Auto-Intent diagnosis results directly from the map. Customers troubleshooting network issues would benefit from the ability to document, share, and retain diagnostic findings without needing to manually recreate or copy the results for external use.
The Duplicate IP and Subnet Manager view does not currently display interface administrative status, making it difficult to distinguish genuine duplicate address conflicts from interfaces that are administratively down and pose no immediate network risk. The view also lacks support for user-defined fields, so there is no way to tag or track individual duplicate entries over time, such as marking known and accepted duplicates versus items that require action. This enhancement would add an interface status column to the Duplicate IP and Subnet Manager view and introduce configurable user fields that allow entries to be tagged and followed through their lifecycle. Customers would benefit from clearer prioritization of true network risks, reduced false alarms from expected duplicate configurations, and improved ability to track remediation progress over time.
NetBrain currently lacks an auto layout option that arranges a traced path in a single flat, linear row; multi-hop traceroute results are instead rendered in a zigzag pattern, which makes associated data views, such as L3 link details, harder to read. This enhancement would introduce a flat, linear auto layout style that positions the hops of a traced path in a straight horizontal line. Providing this option would improve the readability of path-related data views and reduce the manual effort required to reorganize traced path maps for analysis.
NetBrain upgrade and patch packages do not currently include all required Python dependencies, such as paramiko, for offline installation environments. When a required package is missing from the offline package set, administrators cannot install it through the standard offline pip command, causing plugin or feature functionality that depends on it to fail. This enhancement would ensure that all Python dependencies required by NetBrain plugins and features are pre-packaged and validated as part of the upgrade or patch distribution, removing the need for manual dependency installation in offline or restricted environments. This would reduce failed installations and support cases for customers operating in air-gapped or offline server environments.
The Fine Tune page currently does not display devices that are discovered through SD-WAN integrations or through API-based discovery methods, limiting administrators from reviewing and managing these devices alongside traditionally discovered network devices. This enhancement would extend Fine Tune to include SD-WAN and API-discovered devices, giving administrators a consolidated view for tuning and validation. Customers operating hybrid environments with SD-WAN or API-based device onboarding would gain complete visibility into device status without needing to rely on separate tools or manual checks.
The Hostname Changes table under Fine Tune does not currently support sorting by First Discovery time, making it difficult to identify the oldest of two related entries when a device has multiple discovery records. This enhancement would add sortable column functionality for First Discovery time within the Hostname Changes table. Administrators would be able to quickly locate and review the oldest discovery entries, improving efficiency when auditing hostname change history.
NetBrain currently does not guarantee that a QApp produces identical output whether it is run manually or through a scheduled execution. This enhancement proposes ensuring that scheduled QApp runs generate the same accurate output as manual runs for the same device set and configuration. Customers relying on scheduled automation for reporting and compliance need confidence that scheduled results match what would be produced through manual execution, avoiding data integrity concerns in automated workflows.
NetBrain compliance comparison currently requires ADT entries to match running configuration values exactly, with no way to designate a portion of a configuration line as a variable that differs by site or device while still validating the surrounding structure. As a result, customers cannot use a single ADT definition to check configuration lines that contain environment-specific values, such as an interface name and IP address pair that varies across locations. This enhancement would allow ADT entries to include variable placeholders, so a line such as a logging host statement could be defined with variables representing the interface and IP portions while the surrounding syntax remains fixed for validation. Customers managing configuration compliance across many sites with varying device-specific values would be able to build standardized compliance checks without creating separate ADT entries for each site, reducing maintenance effort and improving consistency of compliance validation.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.