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.
Today, when a remediation action is triggered by an Intent Diagnosis condition, the system does not retain any record of a previously triggered remediation change. As a result, the same remediation change is triggered repeatedly each time the condition evaluates as true, even when a related change is already pending or in progress. This enhancement would introduce tracking of the last remediation state triggered by a given condition, making that state available either to remediation logic for conditional suppression or as visible context within the change creation dialog. Customers who require dependent activities to be completed before a change should recur would benefit from reduced duplicate or conflicting change executions and more reliable automated remediation workflows.
NetBrain currently limits AWS-based device group criteria to Resource Name, Account ID, Resource ID, Resource Type, and Region, with no support for grouping devices by AWS resource tags. This enhancement would extend device group creation and dynamic search criteria to include AWS tags as a selectable filter option. Customers managing large AWS environments would benefit from more flexible and precise device grouping aligned with their existing cloud tagging strategies, reducing manual effort in organizing cloud resources.
Golden Engineering Studio currently restricts rule names to a limited character set, preventing the use of special characters within naming conventions. This enhancement would allow special characters to be included in GES rule names, enabling naming structures that align with external formatting or governance standards. Customers who must conform GES rule naming to established internal naming policies would gain the flexibility to do so without workarounds.
NetBrain currently requires users to run the Verify action on each Golden Assessment rule individually, with no option to validate multiple rules at once. This enhancement would introduce a feature-level Verify action that allows users to select and validate multiple Golden Assessment rules simultaneously. Customers managing large rule sets would benefit from reduced validation time and a more efficient assessment workflow.
Network Intent and parser-based execution currently cannot process CLI commands where the primary command keyword appears at the end of the command string rather than as a leading prefix, even though such commands execute successfully through standard CLI Commands. This limits the ability to use Network Intent for device command sets that follow non-standard syntax conventions. This enhancement would extend Network Intent and parser command matching logic to recognize and execute commands regardless of keyword position within the command string. Supporting flexible command formats would allow customers with non-standard CLI syntax to fully leverage Network Intent automation and parsing capabilities without needing to restructure existing command sets.
NetBrain currently limits device CLI access from the mapped device right-click menu to its built-in Smart CLI, with no option to launch an external, user-preferred SSH client. This enhancement would allow administrators to configure a third-party SSH client, such as SecureCRT, as an alternative login method for device access from the map interface. Customers who rely on established third-party terminal tools for session logging, scripting, or personal workflow preferences would benefit from continued use of their preferred client without being restricted to Smart CLI.
NetBrain currently requires users of the TAF-lite API to retrieve Feature Table data through one call and then make a separate call per Network Intent to obtain execution results, which does not scale for environments with large device counts and multiple rules per device. This enhancement would allow custom columns, such as Intent Status Code and execution timestamp, to be included directly in the Feature Table so that all relevant data can be retrieved in a single API call. Reducing the number of required calls would improve scalability and efficiency for customers exporting automation results to external systems such as data lakes.
NetBrain currently does not support capturing command output from Intent execution within the Document Node of a Runbook, leaving generated documents without a record of the commands that were run. This enhancement would add an option to the Document Node allowing command output from Intent execution to be included in the generated document. Customers who must retain execution evidence for change records or ticketing systems would benefit from having a complete, exportable record of commands executed and their results.
NetBrain's discovery and path analysis capabilities currently do not extend beyond the internal network to cover internet segments, public cloud providers, or SaaS applications, limiting end-to-end visibility for hybrid environments. This enhancement would introduce an API-based integration with a third-party internet and cloud monitoring service to extend path analysis and diagnostics to internet-facing destinations, public cloud services, and SaaS applications, along with cross-domain visibility across underlay and overlay network infrastructure and cloud topology. Customers operating hybrid network and cloud environments would gain unified, end-to-end path and topology visibility, reducing the need to correlate data manually across separate monitoring tools.
NetBrain does not currently provide a way to acknowledge an active alert and temporarily suppress it from reappearing while a known issue is being addressed. Once an alert condition is detected, it continues to be reported on the dashboard until the underlying condition is resolved, with no mechanism to pause notifications for issues already being worked on. This enhancement would introduce an alert acknowledgement action that allows a user to mark an alert as acknowledged and suppress it for a configurable time period. Once the suppression period expires, the alert would resume normal reporting if the condition still exists. This capability would reduce alert noise for issues already in progress, allowing teams to focus dashboard attention on new or unresolved conditions.
In distributed deployments with multiple worker servers updating dashboards in parallel, the current update mechanism relies on incrementing and decrementing shared counters based on timestamp heuristics. This approach is susceptible to race conditions, which can produce inconsistent or negative values on dashboard widgets. This enhancement would make the dashboard update mechanism idempotent and safe for concurrent, multi-worker execution, ensuring counter updates are applied consistently regardless of timing or ordering. Reliable, consistent dashboard values are essential for customers operating large, multi-server environments who depend on dashboards for accurate operational visibility and trust in the platform.
NetBrain currently does not show users how many login attempts remain after an incorrect password entry, nor does it display the cooldown period or next allowed login time once an account becomes locked. Failed login entries also require manual deletion from the database rather than being cleared automatically after a defined interval. This enhancement would add visible attempt-remaining and lockout-countdown information to the login workflow, and would introduce an automatic cleanup mechanism for failed login records after a configurable interval. Customers would benefit from clearer account status feedback and reduced administrative overhead in managing lockout data, helping to minimize unnecessary lockouts and improve the overall login experience.
NetBrain currently places several frequently used path discovery options under the Advanced Path Discovery Settings section, where they are easily overlooked by users configuring path behavior. This enhancement would relocate the most commonly used options to the main Path Settings menu, while retaining less frequently used options under Advanced. Improving the visibility of these settings would help customers configure path discovery more effectively without needing to locate options buried in a secondary menu.
The current Start Menu icon does not follow standard app launcher conventions found in modern UI design, which can make navigation less intuitive for users. This enhancement proposes replacing the existing icon with a standard app launcher icon consistent with common UI patterns. Adopting a familiar icon design would improve usability and reduce the learning curve for new users navigating the interface.
NetBrain currently requires users to add a Runbook node to the Favorites panel by opening the hamburger menu on that node and selecting the appropriate option, which adds extra steps to a routine workflow. This enhancement would allow users to drag and drop a Runbook node directly onto the Favorites panel to mark it as a favorite. Customers who frequently reuse specific nodes across Runbooks would benefit from a faster, more intuitive way to manage their favorites without navigating through menus.
NetBrain currently organizes Runbook node types into tabs within the node selection panel, but the Free Text and Favorites sections are not grouped under the Essential tab alongside commonly used node types. This enhancement would relocate the Free Text and Favorites sections into the Essential tab, consolidating frequently accessed node categories in a single location. Customers building Runbooks would benefit from a more intuitive node selection experience and reduced time spent navigating between tabs to locate commonly used node types.
The Runbook editor currently does not provide a way to reorder nodes within a Runbook by dragging them into a new position. Users who need to adjust the sequence of steps must rely on manual reconnection or recreation of nodes, which is time-consuming and prone to error. This enhancement would introduce drag-and-drop functionality that allows users to reposition nodes directly within the Runbook canvas, automatically updating the connections to reflect the new order. Customers building or maintaining complex Runbooks would benefit from a more intuitive editing workflow and reduced effort when adjusting the logical flow of a Runbook.
NetBrain currently places the 'Run All' option for Runbooks within a hamburger menu, requiring users to open a secondary menu to locate and trigger it. This enhancement would surface the 'Run All' option directly within the primary Runbook interface, making it immediately visible without additional navigation. Improved discoverability of this control would reduce the time and effort required for users to execute a full Runbook, particularly for those less familiar with the current menu structure.
The option to create a support ticket is not currently located in the top navigation bar, reducing its visibility to users during daily workflows. This enhancement would relocate the Create Support Ticket action back to the top bar so it remains readily accessible. Increasing visibility of this frequently used feature would help customers initiate support requests more efficiently.
NetBrain currently does not support receiving or processing NetFlow data when devices are configured to export their flow records directly to NetBrain. This limits visibility for customers who rely on flow-based traffic analysis as part of their network monitoring strategy. This enhancement would add native NetFlow collector functionality, allowing NetBrain to receive, parse, and process flow records sent from network devices. Customers would benefit from consolidated flow-based traffic insight within the same platform used for device and path visibility, reducing the need for a separate flow collection tool.
System Management currently does not provide administrators with a way to unlock a user account that has been locked due to exceeding the maximum number of failed login attempts. This enhancement would add an unlock action within System Management, allowing an authorized administrator to manually restore access to a locked account without requiring a password reset or backend intervention. Customers would benefit from faster resolution of account lockouts and reduced dependency on external support channels for routine access issues.
NetBrain's AI Companion and Deep Diagnosis currently process runbook logic and commands as provided, and will reflect errors present in a runbook's underlying logic or commands rather than identifying them as mistakes. This enhancement would enable the AI to cross-reference runbook logic and commands against correlated network engineering knowledge, using retrieval-augmented techniques, to detect and flag likely human-made errors instead of simply reporting flawed output as valid. Customers relying on AI-driven diagnosis would benefit from improved output accuracy and increased confidence that runbook-driven results reflect sound network engineering practice rather than propagating undetected mistakes.
Golden Assessment dashboards are currently organized by zone and display results for all supported protocols, including those a customer does not use, such as ISIS or EIGRP alongside BGP or OSPF. This structure limits the ability to present results in a way that aligns with business priorities or operational relevance, and reduces clarity for teams reviewing assessment data. This enhancement would introduce dashboard views that can be organized around business-relevant groupings rather than zone alone, and that are context-aware based on the protocols and features actually in use within a customer's environment. Customers would benefit from clearer, more relevant assessment views that reduce noise and better reflect their specific network operations.
NetBrain currently allows a Network Intent to be saved even when its diagnosis logic contains an incomplete conditional statement, such as a where condition that has not been fully defined. This can result in intents that fail to evaluate correctly during execution without any indication at the time of authoring. This enhancement would introduce validation that detects incomplete conditional logic when a user attempts to save a Network Intent, displaying an alert and preventing the save until the condition is completed. This capability would help customers catch configuration errors earlier, reducing troubleshooting effort and preventing faulty diagnosis outcomes caused by incomplete intent logic.
The Configlet node in Runbook currently does not provide inline guidance to distinguish between the config parser and golden config options, which can lead to confusion about their intended use. This enhancement would add tooltips or contextual hints within the Configlet node interface to clarify the purpose and difference between these two options. Providing this guidance would help users configure the node correctly on the first attempt and reduce setup errors during Runbook design.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.