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 provide a reliable plugin-based method to retrieve the complete list of discoverable VPC resource IDs for Google Cloud (GCP), which limits the accuracy of include/exclude VPC discovery scoping in GCP environments. This enhancement would introduce a GCP-specific mechanism to fetch and validate discoverable VPC resource IDs, aligning GCP discovery capabilities with those already available for AWS and Azure. Customers managing GCP infrastructure would benefit from more accurate and dependable control over which VPCs are included or excluded during discovery, reducing errors caused by incomplete or outdated resource ID lists.
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.
NetBrain currently requires users to manually assign Layout Tags to devices in order to control their placement within a map layout hierarchy; there is no mechanism to derive tags automatically from a device attribute such as Model. This enhancement would allow tags to be generated or assigned automatically based on the device Model field, so that maps can display devices hierarchically by layer according to their model-derived classification. Customers managing environments with a large variety of device models would benefit from consistent, layered map views without the ongoing manual effort of tagging each device individually.
NetBrain currently couples map editing rights and Intent editing rights within the same role construct, such as the 'Shared Resources' role. Administrators cannot grant a user the ability to run Intents and create or edit their own maps without also granting that user the ability to edit Intents themselves, and users without this role cannot edit maps even after receiving explicit edit access from an administrator. This enhancement would introduce independent role permissions for running Intents, editing Intents, and creating or editing maps, allowing administrators to combine these capabilities as needed for each tier of user. Customers with tiered support teams would benefit from finer-grained, least-privilege access control, allowing elevated map access without unintended exposure of Intent editing capability.
NetBrain does not currently provide a way to import a spreadsheet of IP addresses and resolve DNS hostnames for entries that are not yet discovered devices in the domain. Users must rely on devices already present in the OneIP Table to obtain hostname resolution, which limits usefulness when planning hardware upgrades or replacements that will reuse existing IP addresses and DNS names. This enhancement proposes allowing users to import a spreadsheet of IP addresses into the OneIP Table workflow so that NetBrain performs DNS resolution against that imported list, independent of device discovery status. Customers preparing for hardware upgrades or IP reassignment would benefit from validating DNS hostname mappings in advance, reducing manual lookup effort and improving planning accuracy.
Chatbot automation currently requires a user to manually click through each Network Intent Task node during a troubleshooting flow, even in cases where only one candidate device is available for that step. This adds unnecessary time and manual effort to what should be a streamlined automated process. This enhancement would introduce a setting that allows a specified NIT node to execute automatically when it has only one alternative device, removing the need for manual confirmation at that step. Customers running chatbot-driven troubleshooting flows would benefit from faster resolution times and a more consistent end-to-end automated experience.
NetBrain currently does not summarize or display whether a scheduled Network Intent executed as expected on the PAF page, requiring users to manually review each intent individually to confirm execution status. This enhancement would add an alert mechanism and a consolidated execution summary that flags when a scheduled Network Intent did not run as configured. Providing this visibility would allow customers to detect scheduling failures promptly, reducing the risk of undetected data loss and the manual effort of checking each intent's run history individually.
NetBrain currently calculates and displays node license usage in the Domain Summary using logic that may differ from the calculation used for email notifications, which can result in two different license counts being reported to administrators for the same period. This enhancement would align the license count calculation between the in-application summary and notification emails so that both sources consistently report the same value. Ensuring consistent license reporting would reduce confusion for administrators reviewing license capacity and help prevent unnecessary investigation into perceived license discrepancies.
The Summary Dashboard currently does not display the execution time associated with the underlying automation or data collection run, leaving users without visibility into when the displayed results were last generated. This enhancement would add an execution time field to Summary Dashboard widgets, showing users when the data was last refreshed. Providing this information would help customers assess data freshness at a glance, supporting more confident decision-making and more accurate reporting.
NetBrain currently does not provide a way for engineers to observe live CLI output on a device as a configuration change is being executed through Change Management, leaving them without real-time insight into device responses or errors during the process. This enhancement would introduce a read-only CLI console that streams the live command output on the target device while a Change Management task is running, displaying prompts, responses, and any errors as they occur. This would allow engineers to confirm configuration success or quickly identify device-reported issues in real time, reducing reliance on post-execution logs and manual verification steps.
NetBrain currently offers no mechanism to update Automated Data Tables (ADTs) or Network Intents that reference a device hostname once that hostname has changed. When a hostname is renamed, any ADT or Intent tied to the prior hostname becomes invalid, and administrators must manually recreate the affected objects rather than update the existing reference. This enhancement would introduce a refactoring capability that allows ADT and Intent definitions to be updated to reflect a renamed hostname while preserving the underlying logic and configuration. Customers who periodically rename devices would benefit from reduced administrative effort and avoid the risk of losing established automation work.
NetBrain currently does not provide a way to export device configuration backups that are approaching the end of their retention period for external storage, nor does it support re-importing previously exported backups back into the system when needed. Customers who wish to shorten their retention window are left without a supported path to retain access to older configuration data. This enhancement proposes adding an export function for historical configuration backups that fall outside a shortened retention period, along with a corresponding restore function to bring externally stored backups back into NetBrain when required. This would let customers reduce on-platform storage retention while preserving the ability to recover and reference older configuration data as needed.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.