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 does not allow the sections within the Runbook right-side panel to be resized, which makes it difficult to fully view long commands or lengthy device names within the fixed display area. This enhancement would add resizable controls to each section of the right panel, allowing users to expand or collapse individual sections as needed. Customers working with longer command outputs or extended device naming conventions would benefit from improved readability and reduced effort when distinguishing between panel sections.
The Change Analysis Report currently does not clearly indicate whether each detected difference represents an addition, removal, or modification within its respective category, requiring users to interpret the nature of each change manually. This enhancement would add explicit labeling of each change entry as ADDED, REMOVED, or MODIFIED, organized by category, within the report output. Customers reviewing configuration changes would benefit from faster, more accurate identification of change types, reducing manual review effort during audits and troubleshooting.
NetBrain currently allows an image file to be added to a map page, but the image renders at a very small, icon-sized display regardless of the source file's actual dimensions. This enhancement would add an option to display attached image files at full size on the map page, rather than scaling them down to an icon. Customers who want to attach pre-built reference diagrams, such as exported site visio drawings saved as JPEG or PNG, would be able to view them clearly within the map context without opening a separate file.
NetBrain currently applies a follow-up intent to all L3 neighbors listed in the neighbor table, without allowing users to scope execution to neighbors that share a specific relationship type, such as BGP or OSPF. This enhancement would add a filtering option so users can select one or more L3 relationship types and run the follow-up intent only against matching neighbors. Customers working with large L3 neighbor tables would gain more targeted and efficient troubleshooting, avoiding unnecessary processing of unrelated neighbor relationships.
When a triggered run occurs, the associated Data View Template does not automatically apply to the resulting map, so the map shown in the Incident Portal does not reflect the intended data view until a user manually logs into the NetBrain console, applies the data view, and saves the map. This enhancement would allow the configured Data View Template to be applied automatically as part of the triggered run, without requiring manual console intervention. Removing this manual step would ensure that diagnostic and contextual data appears immediately in the Incident Portal, supporting faster triage and reducing delays for users responding to incidents.
NetBrain currently does not detect Inter-Switch Links (ISL) between switches in a Brocade VCS Fabric, which prevents these fabrics from being automatically drawn on the topology map. This enhancement would add discovery logic to identify ISL connections within Brocade VCS Fabric environments and represent them as links on the map. Customers operating Brocade VCS Fabrics would benefit from accurate, automatically generated topology views without needing to manually add these links.
NetBrain currently requires users to manually click an option to show intent diagnosis results on the map after an intent has run through a runbook; results are not surfaced automatically. This enhancement would allow the map to display intent diagnosis results by default whenever an intent executes as part of a runbook, removing the extra manual step. Customers running runbooks for network diagnosis would gain immediate visibility into results directly on the map, improving efficiency during troubleshooting workflows.
NetBrain currently does not update a previously approved change record back to New status when the corresponding change request is reverted to New within ServiceNow, leaving the two systems out of sync after such a state change. This enhancement would extend the ServiceNow change integration to detect when a synchronized change is moved back to New in ServiceNow and automatically revert the associated NetBrain change to the same status. Maintaining consistent change status across both platforms would reduce manual correction and help teams rely on accurate, synchronized change records during their approval workflows.
NetBrain currently has no mechanism to automatically detect when a new device is physically connected to the network, and the Change Management module does not include a built-in SFTP process for transferring a prior device's configuration to its replacement. As a result, switch replacement requires manual discovery initiation and manual configuration transfer steps. This enhancement would introduce automatic discovery of newly connected devices and a built-in SFTP capability within Change Management to push the retiring device's saved configuration directly to the replacement device. Customers managing incident response and hardware lifecycle events would benefit from a faster, more consistent switch replacement process with reduced manual effort and downtime.
NetBrain's custom auto grouping layout currently does not support defining DMVPN and MPLS map objects as part of the layout configuration, so these objects cannot conform to the automatic grouping and positioning structure applied to other device types. This enhancement would allow DMVPN and MPLS map objects to be included as definable elements within custom auto grouping layout rules, enabling consistent automated placement alongside other network elements. Customers managing WAN topologies with DMVPN and MPLS clouds would benefit from consistent, automated map organization without manual repositioning of these objects.
When running a historical path calculation for a specific point in time, the calculation currently fails if no benchmark data exists within the configured time window around that point, requiring users to widen the window manually. This enhancement would allow the path calculation to use the most recent available data at or before the selected time, rather than requiring data to fall strictly within a fixed window. Customers would benefit from historical path calculations that remain reliable even when device data collection has gaps, reducing failed calculations and manual window adjustments.
The Do-Not-Scan list, which relies on hostname matching, does not currently extend its exclusion logic to devices added or discovered through API-based methods. As a result, devices intended to be excluded from scanning may still be processed when introduced via API integrations. This enhancement would extend Do-Not-Scan enforcement to recognize and exclude API-discovered devices using the same hostname matching logic applied to other discovery methods. Customers using API-based device onboarding would benefit from consistent exclusion behavior and reduced risk of scanning devices that should remain excluded.
The Interface Report does not currently include an Interface Type field, even though this data is available from device command output such as 'show interface status.' This enhancement would add an Interface Type column to the Interface Report, allowing the field to be displayed and referenced alongside existing interface attributes. Customers performing network audits and troubleshooting would benefit from having interface type readily visible without needing to cross-reference raw command output.
NetBrain's REST API does not currently provide a documented endpoint for retrieving Golden Engineering Studio data, such as golden rule details or associated device counts. This limits customers who want to build automated reporting or compliance workflows around golden rule results without relying on the user interface. This enhancement would introduce REST API endpoints that expose Golden Engineering Studio rule data, including rule definitions and associated device metrics, for programmatic retrieval. Customers integrating NetBrain with external reporting or compliance systems would benefit from consistent, automated access to golden rule information without manual lookup.
NetBrain currently supports only standard username and password authentication for MongoDB connections, with no ability to specify an authSource database or an authentication mechanism (authMech) required by certain MongoDB deployment configurations. This enhancement would add configurable authSource and authMech fields to the MongoDB connection settings, allowing administrators to align NetBrain with their specific MongoDB authentication requirements. Customers running MongoDB environments that require a designated authentication database or a non-default authentication mechanism would benefit from successful connectivity without needing workarounds or configuration changes on the database side.
NetBrain currently does not provide a way to run ping connectivity checks in bulk between multiple source devices and multiple destination IP addresses, nor to export the resulting reachability status with source and destination identifying information in a single operation. This enhancement proposes adding a bulk ping test capability that allows a user to define a set of source devices and a set of destination IPs, execute ping tests across all source-destination pairs, and export the results, including source and destination hostname and IP address along with the ping outcome, to a CSV file. Customers managing large environments with many application servers and remote sites would benefit from being able to validate network reachability at scale without performing manual, one-at-a-time connectivity checks.
NetBrain currently does not notify administrators when a user's assigned role or permission set changes, including changes that occur indirectly through SSO or identity-provider role mapping. Administrators must manually cross-reference multiple systems to detect that a user's effective permissions have changed, and there is no record of which account initiated the change. This enhancement would introduce an alerting mechanism that notifies designated administrators whenever a user's role or permission mapping changes, along with a record of the account that triggered the change. This capability would help organizations detect unauthorized privilege escalation, maintain continuity when administrative responsibilities transfer between staff, and support ongoing security and compliance review without manual investigation across systems.
NetBrain currently requires LDAP connection details to be entered through discrete configuration fields, without support for specifying the connection as a single LDAP URI. This enhancement would allow administrators to configure an LDAP server connection using a standard URI format, encapsulating host, port, and other connection parameters in one string. Customers who manage LDAP configurations through URI-based standards would benefit from simplified setup and consistency with their existing directory service tooling.
NetBrain currently does not support updating a single cell within an Automated Data Table (ADT) through the Import File Wizard. To change one value, administrators must either declare an entirely new column or re-import all data for the affected column, even when only one record requires modification. This enhancement would allow administrators to update individual cell values directly during the import process without requiring a full column re-import or the creation of a new column. Customers maintaining ADTs with frequent minor data corrections would benefit from reduced manual effort and a more efficient import workflow.
NetBrain currently does not support successful execution of scheduled QApp tasks on SD-WAN devices that communicate through the API Front Server, even though the same scheduled tasks run successfully on switches within the same device group. This enhancement would extend scheduled QApp execution support to SD-WAN devices connecting via the API Front Server, ensuring consistent behavior across device types. Customers relying on scheduled compliance and audit QApps benefit from complete, uninterrupted automation coverage across their full device inventory, including SD-WAN environments.
NetBrain currently cannot represent connectivity to a Google Cloud VPC peering endpoint when that peered VPC is not discoverable or accessible within the domain, leaving the relationship absent from topology maps. This enhancement would allow NetBrain to display a placeholder or logical representation of the peering connection to the unknown VPC, even when the peer device itself cannot be discovered. Customers operating multi-VPC or multi-account GCP environments would gain more complete topology visibility and a clearer understanding of cross-VPC connectivity without requiring full access to every peered environment.
NetBrain currently relies on CLI-based or SNMP-based polling to retrieve BGP routing information and does not support BMP (BGP Monitoring Protocol) as a data collection method for BGP route monitoring. This enhancement would add BMP support, allowing NetBrain to receive real-time BGP route updates and state changes directly from routers configured as BMP stations. Customers with large or dynamic BGP environments would benefit from more timely and lower-overhead BGP route visibility, reducing dependence on repeated polling and improving the accuracy of route change detection.
NetBrain currently does not provide a way to export Device Access Policy configurations, including the policies that have been created and the privileges assigned to each user, in a structured file format. This enhancement would add an export capability for Device Access Policy data, allowing administrators to generate a report listing all defined policies along with their associated user privilege assignments. Customers operating under internal security and compliance requirements would benefit from having a documented, exportable record of access policy configurations to support audits and reviews without relying on manual screenshots or live walkthroughs.
NetBrain currently has no mechanism for storing a shared Python class, library, or package in a central location that can be imported into multiple QApps or plugins; users must duplicate the same code within each QApp that needs it. This enhancement proposes support for importing custom Python resources, such as .py files, pylib, or pypackage, into a shared repository and allowing any QApp or plugin to reference them using standard Python import syntax. Centralized reuse of Python code would reduce duplicate maintenance effort and improve consistency across automation scripts.
NetBrain currently applies SSH algorithm and cipher settings at a global level, which means enabling older or legacy SSH algorithms to support specific devices requires enabling those algorithms across the entire environment. This weakens the overall security posture for devices that support modern, more secure algorithms. This enhancement would allow administrators to define SSH algorithm policies on a per-device or per-device-group basis, such as through a device-specific SSH configuration file, rather than applying a single global setting. Customers who must maintain connectivity to legacy devices requiring older SSH algorithms would be able to do so without compromising security compliance for the rest of their environment.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.