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 dashboards are currently built around intents and per-site alert counts, and generating hierarchical operations views requires substantial manual effort since there is no way to automatically create a dashboard for each row of an Automated Data Table. This enhancement would add the ability to automatically generate a dashboard for every row in an Automated Data Table, enabling a progressive drill-down experience from a global view down to regional, sub-regional, and specific issue levels such as protocol state changes or configuration drift. Customers building network operations center style views would benefit from significantly reduced manual dashboard construction effort and a more consistent, scalable way to monitor network health across organizational hierarchies.
Today, follow-up Network Intents that have remediation enabled do not support distinct, intent-specific remediation templates; remediation logic is currently applied in a shared manner across follow-up intents. This enhancement would allow each follow-up intent to be configured with its own separate remediation template, tailored to the specific condition it diagnoses. Customers using multi-step diagnostic workflows with remediation enabled on follow-up intents would gain more precise and reliable automated remediation, reducing the risk of applying a mismatched or overly generic remediation action.
Change Template variables currently require manual entry each time a change is executed, with no option to select from existing config parameters or previously used values. This enhancement would allow variables to be populated by selecting from config parameters generated through Golden Config Rule Discovery, as well as from a list of saved or customer-added entries. This capability would reduce repetitive manual entry, improve consistency across change executions, and speed up the change remediation process.
The Runbook Document node currently allows granular selection of which runbook components to include in a Word export, but it does not provide any option to select or customize a Word template, such as styles, fonts, or branded layouts, in the way that the Map Export to Word feature does through its 'Select Style' option. This enhancement proposes adding Word template customization to the Runbook Document node, giving users the ability to choose from predefined styles or apply branded layouts consistent with other export workflows. Supporting this capability would help customers maintain consistent formatting and branding across all exported documentation, reducing manual reformatting after export.
When a Feature ADT contains a large number of follow-up intents, users must manually scroll through the full list to locate and select the intents they need, which is time-consuming and increases the risk of missing critical intents. This enhancement would add a keyword-based search or filter to the intent selection interface, along with a visible count of currently selected intents. Providing search and selection-count capabilities would help users quickly locate relevant intents and validate their selections before execution, improving accuracy and efficiency in large-scale automation workflows.
NetBrain currently does not provide a way to disable auto remediation when a Network Intent contains multiple follow-up intents that each include remediation templates. In this scenario, remediation actions may execute automatically across all applicable follow-ups without an option to suppress that behavior at the intent level. This enhancement would introduce a "Disable Auto Remediation" setting that can be applied to intents with multiple remediation-capable follow-ups, giving users explicit control over whether automated remediation runs. Customers managing complex diagnostic workflows would gain greater control over automation behavior, reducing the risk of unintended remediation actions across multiple follow-up paths.
When installing rules through Rule Discovery, users must manually unselect each rule individually if they only want to install a subset, such as vendor-specific rules. This enhancement would add an 'Unselect All' or 'Clear Selection' action to the Config Rule Template selection interface, allowing the full list to be cleared in a single action before filtering and selecting the desired rules. Customers installing targeted rule subsets would benefit from a faster, less error-prone selection workflow.
NetBrain currently requires users to manually generate Golden Assessment reports, with no option to schedule recurring report generation. This enhancement would introduce a scheduling capability for Golden Assessment reports, allowing users to configure recurring generation on a defined interval, such as daily, weekly, or monthly, with automatic delivery to designated recipients. Customers relying on Golden Assessment for ongoing compliance and configuration validation would benefit from consistent, timely reporting without the need for manual intervention.
Network Intent currently does not carry device-level or intent-level status codes generated in one diagnosis forward into a subsequent diagnosis within the same intent, requiring each diagnosis to independently determine its own status. This enhancement would allow a status code established in an earlier diagnosis to be referenced and reused by later diagnoses within the same intent. Customers building multi-step diagnostic logic would benefit from more consistent and accurate status reporting without needing to duplicate status determination logic across each diagnosis.
Within Golden Config Discovery, the device groups used for applying configuration and features do not automatically update when new devices are added to the environment, requiring manual intervention to keep group membership current. Additionally, when new devices are incorporated, the process only applies configuration to them without performing verification, which leaves administrators without confirmation that the applied configuration is correct. This enhancement proposes that Golden Config Discovery automatically update its associated device groups as device inventory changes, and that newly added devices go through both an apply and a verify step as part of the same workflow. Customers managing dynamic environments would benefit from reduced manual maintenance and greater confidence that configuration changes are both applied and validated on new devices.
NetBrain currently does not consistently highlight all trunk links on L2 topology maps when a bus element is part of the connection path, leaving some trunk segments visually indistinguishable from non-trunk links. This enhancement would extend the trunk highlighting logic so that all trunk connections, including those passing through bus elements, are rendered in the same highlighted color. Consistent trunk highlighting across all connection types would improve map readability and reduce the risk of misinterpreting network topology during troubleshooting.
NetBrain currently does not provide a way to selectively apply Site-Level Health Check Network Intents based on site attributes, requiring the same NI logic to be applied uniformly across all sites regardless of differences in device types, protocols, or WAN architecture. This enhancement would allow administrators to define site-level properties, such as architecture type or connectivity model, and use those properties as criteria to scope which sites a given Health Check NI applies to. This would allow customers operating multiple site types to tailor health checks to the devices and protocols relevant to each site category, reducing irrelevant alerts and manual NI management effort.
NetBrain's REST API and Python API currently do not provide a method to programmatically execute the global 'Full Search' function that is available in the web UI, requiring users to submit each search manually through the interface. This enhancement would introduce an API endpoint that accepts full search queries and returns results equivalent to the UI-based search. Customers who need to run large volumes of searches would benefit from the ability to automate this process, reducing manual effort and enabling integration with external workflows.
NetBrain currently does not preserve complete Network Change task and Runbook information when the task is exported from the Change Management module and later imported into another environment. As a result, the imported task can appear without the detail needed to review or troubleshoot the original configuration and results. This enhancement would allow Network Change tasks to be exported with their full underlying information intact, so that importing the file into a different environment reproduces the same or substantially similar detail seen by the original user. This would give support and administrative staff the ability to review a customer's Network Change task locally with complete context, improving troubleshooting accuracy and reducing back-and-forth data collection.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.