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.
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 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 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 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.
NetBrain currently ties the ability to create or edit Network Intents to the broader 'Shared Resources and File Management' privilege, so removing that privilege from a user also removes their access to standard public folders. Administrators cannot control Network Intent authoring rights independently of general shared resource access. This enhancement would introduce a distinct privilege specifically for creating and editing Network Intents, separate from the shared resources and file management permission. Organizations using shared user pools, such as technicians who need public folder access but should not be able to author Network Intents, would gain the ability to restrict NI creation and editing to designated administrators without impacting other shared resource access.
NetBrain currently renders the A-to-B path line using a single static style, which does not visually indicate direction or sequence when the path loops through the same object multiple times. This makes it difficult for users to follow the path accurately in complex or looping scenarios. This enhancement would introduce an animated or gradient rendering option for the A-to-B path line to convey directionality and sequence more clearly. Customers troubleshooting complex paths with repeated traversal of the same object would benefit from improved visual clarity, reducing the time spent manually tracing the path order on the map.
NetBrain's REST API does not currently provide a method to execute CLI commands directly on devices and return the output through an API call. This enhancement would introduce a new API endpoint that allows external systems to send CLI commands to one or more devices and receive the resulting output programmatically. Customers integrating NetBrain with automation, orchestration, or scripting tools would gain the ability to perform ad hoc command execution and data retrieval without relying on the NetBrain user interface, improving efficiency for automated network operations.
NetBrain currently does not automatically identify or add the physical interfaces that interconnect devices participating in a BGP or EIGRP peering relationship when those devices are added to a map. Users must manually determine and add the correct physical interfaces to represent the underlying Layer 2 connectivity between routing protocol peers. This enhancement would allow NetBrain to detect BGP or EIGRP peer relationships between devices on a map and automatically add the physical interfaces that logically interconnect them. Customers with routing-protocol-driven topologies would gain more accurate and complete maps with reduced manual effort, improving topology accuracy and troubleshooting efficiency.
NetBrain currently adds devices to the domain during discovery even when the device is not accessible via SNMP or CLI, and it does not provide a way to exclude devices from onboarding based on the outcome of CLI access attempts alone. This requires administrators to manually identify and remove inaccessible or partially accessible devices after they have already been added. This enhancement would introduce configurable domain management discovery exclusion rules tied to SNMP and CLI access results, allowing administrators to prevent a device from being added to the domain when both SNMP and CLI are unreachable, or when CLI access specifically fails. Customers managing large or sensitive environments would benefit from cleaner, more accurate domain inventories and reduced manual cleanup effort following discovery.
NetBrain path trace and traceroute-based mapping do not consistently display the ingress and egress interfaces for each hop, and in some cases map an incorrect interface on a path segment, such as when a tunnel is involved. This enhancement would extend path calculation logic to reliably identify and render the correct ingress and egress interfaces connecting each segment of a calculated path. Consistent, accurate interface-level detail would improve troubleshooting confidence and reduce the need for manual verification of path segments.
NetBrain currently does not provide a way to update a ServiceNow ticket via API and attach the corresponding NetBrain troubleshooting runbook document to that ticket. This enhancement would extend the ServiceNow API integration to allow the generated runbook document to be attached directly to the associated ticket during an automated update. Customers using ServiceNow for incident and change management would benefit from having troubleshooting context and supporting documentation available directly within the ticket, reducing manual effort and improving cross-tool visibility during incident resolution.
NetBrain currently displays a licensing warning popup to all users, including standard daily users, with no option to limit this notification to administrators only. This enhancement would introduce a global, role-based setting that allows administrators to suppress the licensing warning popup for non-administrative users while preserving its visibility for administrators. Customers would benefit from reduced confusion among standard users who have no ability to act on licensing warnings, and administrators would retain the visibility needed to manage license status.
NetBrain currently does not display traceroute results on the map after a trace has been run, requiring users to reference the data separately rather than viewing it in context. This enhancement would automatically add traceroute results to the map upon completion of the trace and would display those results when a trace path is subsequently selected. Providing this visibility would let customers reference traceroute data directly within the map view, reducing the need to cross-reference separate outputs during troubleshooting.
When a device is added to the CLI Commands step of a Runbook, the commands already configured for other devices in that step are not made available to the newly added device, requiring users to manually re-enter each command. This enhancement would allow CLI commands already applied to existing devices in a Runbook step to be automatically extended to newly added devices. This capability would reduce manual re-entry effort and help ensure consistent command coverage across all devices in a Runbook.
NetBrain currently adds interfaces to a map when a device is added without regard to whether those interfaces are part of an actual physical connection to another device already present on the map, which can result in unrelated or random interfaces appearing on the map. This enhancement would allow the map-building process to add only those interfaces that have a physical connection to another device on the map, excluding interfaces with no relevant connection. Limiting interface inclusion in this way would reduce map clutter and the need for manual cleanup, improving readability and accuracy of topology maps.
NetBrain currently requires CLI credentials used in Change Management to be manually maintained and re-tuned whenever passwords change, even in environments where device authentication is already tied to an SSO-integrated identity provider such as TACACS or ISE. This enhancement would allow administrators to configure Change Management CLI authentication to use SSO-based credentials by default, while retaining the option to specify alternate CLI credentials for devices or scenarios where SSO is not applicable. Customers operating in SSO-integrated environments would benefit from reduced administrative effort and faster, more reliable change execution, since credentials would no longer need to be manually updated each time passwords rotate.
Compare nodes within Runbooks currently do not support target device qualification, a filtering capability available on other node types that limits which devices from a prior step are processed. This enhancement would extend target device qualification support to Compare nodes, allowing users to define qualification criteria consistent with other Runbook node types. Customers running multi-step Runbooks would benefit from more precise control over which devices are included in comparison operations, reducing manual filtering and improving Runbook accuracy.
The Function Portal currently does not provide a way to display Intent execution results to portal users, limiting visibility into compliance and monitoring outcomes for those who access the network only through this interface. This enhancement would add the capability to surface Intent results directly within the Function Portal. Customers who rely on the Function Portal for restricted or external access would gain visibility into Intent-based results without requiring full platform access.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.