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 Runbooks currently do not provide a way to duplicate an existing node within a Runbook, including its full configuration such as CLI commands, golden config rules, intent settings with task variables, or configlet parsers. Users must manually recreate a node and re-enter all settings when a similar validation step is needed elsewhere in the same Runbook, such as when building pre- and post-change comparison steps. This enhancement would add a 'Duplicate Node' option within the Runbook editor, allowing a node and its configuration to be copied to a new node with minimal manual re-entry. Customers performing change validation workflows would save setup time and reduce configuration errors when replicating complex node settings across pre- and post-change steps.
When the 'Ignore Order of Lines' option is used together with masked or ignored keywords in a Golden Configuration match pattern, the comparison logic can fail to detect missing or extra configuration lines between the golden and target configs, since masking causes multiple lines to appear identical and order-independent matching treats them as present regardless of actual count or placement. As a result, no alert is triggered and the details view shows no configuration difference, even though a real discrepancy exists. This enhancement would add a secondary verification step to the alert condition logic specifically for checks using 'Ignore Order of Lines,' confirming that an actual line-count or content difference exists before suppressing an alert. Customers relying on order-independent, masked-pattern compliance checks would gain more reliable alerting and reduce the risk of undetected configuration drift.
Boolean Network Intent variables currently accept mixed-case values, such as "True" or "TRUE" alongside "true," without validation, and there is no error shown when a case variant is entered during variable creation. In addition, variable definition guidance instructs lower-case true/false while the diagnosis step presents a dropdown using upper-case True/False, creating inconsistency between the two areas. This enhancement would add validation to enforce a single consistent case format for Boolean variable values at creation time, and align the case format shown in variable definition with the case format presented in diagnosis. Standardizing case handling would reduce configuration errors and eliminate confusion for customers building and maintaining Network Intents with Boolean variables.
Search currently supports lookups by DNS name but does not recognize switchport values, such as a switch and interface identifier, as valid search input. This enhancement proposes extending search functionality to accept switchport values so that users can locate the corresponding device or table entry directly. Customers troubleshooting connectivity by switchport would benefit from faster lookups without needing to cross-reference other tables or rely on alternate identifiers.
NetBrain path calculation currently does not reliably determine the correct traversed path when a VLAN is stretched across multiple sites or devices, unless the user manually specifies the gateway to use. Without manual intervention, the calculated path can diverge from actual traffic flow in these environments. This enhancement would extend the path calculation engine to automatically identify the correct gateway or next hop when tracing across a stretched VLAN topology, removing the need for manual gateway selection. Customers operating stretched VLAN architectures would gain accurate, automatic path visibility, reducing manual verification effort during troubleshooting.
NetBrain currently does not support scoping Azure discovery by individual resource groups, requiring administrators to discover resources at a broader subscription or tenant level. This enhancement would allow users to select specific Azure resource groups as the discovery scope, so that only resources within the chosen groups are included. Customers managing large or segmented Azure environments would benefit from more targeted discovery, improved organization of cloud resources, and reduced time spent mapping unnecessary infrastructure.
NetBrain's Golden Engineering Studio currently does not reliably reflect the true state of unused pattern lines and unmatched lines within a match pattern scenario, as the associated counters can increment even when no such lines are present in the scenario. This enhancement would ensure that unused pattern line and unmatched line counters are calculated and displayed accurately, matching the actual scenario content. Customers relying on these counters to verify configuration compliance and troubleshoot match pattern scenarios would gain accurate, trustworthy reporting without needing to manually cross-check the underlying scenario data.
The Word Document Content Template for Network Intent reports does not currently offer an option to include the parsed configuration snippet that an Intent references, requiring users to manually embed relevant config text within diagnosis messages instead. This enhancement would add a selectable field in the Content Template that inserts the parsed configuration segment associated with the Intent directly into the exported report. Customers who generate assessment or compliance reports would benefit from clearer, more complete documentation without needing manual workarounds to surface the underlying configuration data.
NetBrain's Runbook Compare node currently supports comparing data collected from the same device over time, but it does not provide a way to directly compare the output of two different devices against each other on a line-by-line basis. This enhancement would add an option to the Compare node allowing users to select two distinct devices and view their command output or table data compared side by side, line by line. This capability would help network teams quickly identify configuration or state differences between paired or redundant devices without manual cross-referencing.
NetBrain currently only supports exporting Runbook node results as a whole, requiring users to run a global export and then search through the full result set to locate data for a specific device or command. This enhancement would add contextual export options, accessible through right-click, that allow a user to export the retrieved data for a single device within a node, or the command output for a single command executed against a device, as an individual file. Providing this granular export capability would let customers quickly retrieve the specific data they need without navigating through large consolidated exports, improving efficiency for troubleshooting and documentation tasks that focus on individual devices or commands.
NetBrain currently does not provide a way to unpublish prompts within AI Bot once they have been published. This enhancement proposes adding an option to unpublish previously published prompts, whether individually or in bulk. Customers would benefit from improved control over prompt lifecycle management, allowing them to retract outdated or incorrect prompts without relying on manual workarounds.
The QApp alert node currently displays only the most recently triggered alert message, even when multiple alert conditions occur on a map, while the map itself correctly surfaces all triggered alerts. This enhancement would update the alert node to append and retain all triggered alert messages rather than overwriting with only the latest one. Customers relying on the alert node to track multiple simultaneous or sequential alert conditions would gain complete visibility into all triggered alerts, supporting more accurate monitoring and diagnosis.
NetBrain's Golden Assessment Library currently does not include validated assessment content for Cisco Firepower devices, leaving customers without out-of-the-box configuration compliance checks for this platform. This enhancement would extend the Golden Assessment Library to natively support Cisco Firepower devices, enabling standard assessment and compliance checks through Deep Diagnosis and Runbook Companion workflows. Customers operating Cisco Firepower devices would benefit from consistent, supported assessment coverage without needing to build and maintain custom checks.
The Observability Dashboard folder and file list currently requires users to navigate into a specific folder before viewing its contents, and the search box is not positioned on the left panel by default as it is in NI. This enhancement would update the folder/file list behavior in the Observability Dashboard to match the NI standard, displaying the search box on the left panel by default and allowing users to view all files without first clicking into a folder. Aligning this behavior across products would reduce unnecessary navigation steps and provide a more consistent, intuitive experience for users familiar with the NI interface.
NetBrain currently does not provide a single, consolidated dashboard that presents the connectivity and availability status of all discovered devices in an easily digestible format for administrators. Users must rely on multiple discrete widgets, reports, or manual drill-downs to assemble a comprehensive picture of device reachability and health across the network. This enhancement would introduce a dedicated availability and connectivity dashboard that aggregates status across the full set of discovered devices into a unified, user-friendly view. Customers evaluating or replacing legacy network management tools would benefit from faster, centralized visibility into device availability, reducing the need for manual correlation across separate reports and improving operational efficiency.
Network Intent currently requires users to manually recreate identical sections or logic blocks across multiple, separate intents, and any update to shared logic must be repeated individually in each intent. This enhancement proposes a mechanism to define reusable intent sections, such as through a structured format, along with the ability to import specific diagnosis blocks or sections directly from one intent into another. Customers building and maintaining large libraries of intents would benefit from reduced redundancy, faster intent development, and improved consistency when shared logic needs to be updated.
NetBrain currently displays diagnostic messages during Network Intent execution that can misrepresent a Front Server login failure as an actual network error, since the message wording does not distinguish between a connectivity issue and an authentication failure. This enhancement would refine the error handling logic so that login failures are clearly identified and labeled separately from genuine network-level errors. Providing accurate, distinct diagnostic messaging would reduce troubleshooting time and prevent misinterpretation of the true network state.
NetBrain's discovery and benchmark driver for F5 Load Balancer devices currently does not retrieve running configuration data, leaving a gap in configuration visibility for this platform. This enhancement would add support for the 'list all-properties recursive' command within the F5 Load Balancer driver so that running configuration can be captured consistently. Customers managing F5 Load Balancer devices would benefit from complete configuration data being available for benchmarking, assessment, and troubleshooting workflows.
NetBrain currently does not display route table data for virtual routers on Palo Alto devices within device properties, even when the underlying route table commands have been imported successfully. This enhancement would ensure that route table data collected for each virtual router is correctly parsed and surfaced in the device properties view. Customers managing multi-virtual-router Palo Alto environments would gain accurate and complete routing visibility, reducing the need for manual verification of routing data.
NetBrain currently does not provide a Copy Path option within Golden Assessment Rules, requiring users to locate the corresponding rule in the Golden Config Browser to retrieve its path before it can be referenced in a Network Intent for remediation scripting. This enhancement would add a Copy Path action directly within the Golden Assessment Rule interface, aligning its functionality with the Golden Config Browser. Customers building remediation Intents from Golden Assessment results would save time and avoid switching between modules to obtain rule paths.
NetBrain's audit log currently does not capture REST API call activity, so administrators have no way to determine how frequently or by which methods external systems or teams are invoking the API to retrieve data such as device or IP table information. This enhancement would extend audit logging to record REST API calls, including the endpoint invoked, the calling user or service account, and a timestamp for each call. Administrators would benefit from improved visibility into API usage across teams and integrations, supporting better governance and understanding of how external systems consume NetBrain data.
The Golden Config Generator does not currently offer a 'show in frontend' option, while this capability is already available for the Golden Intent Generator. This enhancement would extend the 'show in frontend' toggle to the Golden Config Generator, aligning its configuration options with those already provided for Golden Intent. Adding this consistency would give customers a uniform experience across golden engineering tools and reduce confusion when configuring visibility settings for generated content.
The Golden Config export function currently outputs only the device, current configuration, and golden configuration data, without including the missing lines or extra lines identified during the comparison. This enhancement would extend the export to include both missing lines and extra lines alongside the existing exported data. Customers reviewing compliance results outside the platform would gain complete visibility into configuration discrepancies without needing to cross-reference the export against the original comparison view.
NetBrain currently does not provide a way to export or propagate tags manually created on a Golden Feature or Golden Intent into the corresponding ADT Intent Column when that data is replicated. This enhancement would allow tags defined on the seed intent to automatically carry over into the ADT Intent Column upon replication. Enabling this tag propagation would allow customers to build and organize wrapper intents based on tag values, improving reusability and reducing manual re-tagging effort.
Building connectivity network diagrams that depict both primary and secondary paths currently requires manual plotting, which is time-intensive for individual diagrams and significantly more so for consolidated views covering multiple components. This enhancement would introduce automated generation of network diagrams that identify and display both primary and secondary connectivity paths for each connection, reducing reliance on manual layout work. Customers who must produce accurate connectivity diagrams for audit and project documentation purposes would gain substantial time savings and more consistent, repeatable diagram output.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.