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.
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.
NetBrain's chatbot default node output currently surfaces only intent-level Msg/Status Code information. When an intent's status code level changes to device level, chatbot flows built against the prior intent-level output no longer display any result. This enhancement would update the chatbot default node output to include both intent-level and device-level status codes, or default to device-level status code, and would apply equivalent handling to existing chatbot definitions that reference only intent-level status codes. Customers would benefit from consistent chatbot behavior across product versions, avoiding silent result gaps when underlying status code levels change.
New users currently have no guided starting point when they first access the product, and the interface offers no contextual explanation of available features, which forces reliance on external documentation or training to become productive. This enhancement would introduce an onboarding wizard for first-time users along with contextual help bubbles placed throughout the interface, providing brief in-product explanations of key features and workflows as users encounter them. Customers new to the platform would be able to orient themselves and begin working more quickly, reducing the learning curve and dependence on formal training resources.
Path-Based Automation currently operates separately from the Golden Automation List (GAL) and requires use of the path browser, making it less accessible than other automation features. Publishing path intents to NB Insight also relies on a workflow that is difficult to locate, and there is no integrated way to manage path intents alongside other automation workflows or share and execute them without sending individual paths to dashboards. This enhancement would integrate path-based automation into GAL and streamline the publishing process for path intents to NB Insight. Customers would benefit from a more consistent automation experience and reduced effort when managing and sharing path-based diagnostics.
NetBrain currently does not provide contextual guidance to help users transition between related features, such as moving from chatbot interactions to change template workflows. Given the density of the interface, users can find it difficult to understand how these features connect or what steps to take next. This enhancement would introduce integrated in-app guidance, such as contextual tooltips, workflow prompts, or a guided walkthrough, to orient users as they move between related capabilities. Providing this guidance would reduce confusion, shorten the learning curve, and help customers navigate the platform's features more efficiently.
Manual input editing controls in the chatbot interface, such as the icon used to modify an existing input value, are not visually discoverable to users today, which can make it difficult for users to realize that editing is possible. This enhancement would redesign the manual input editing affordance to be more visible and intuitive, such as through clearer iconography, labeling, or persistent visibility rather than a hidden control. Improving discoverability of this function would reduce user confusion and support a more efficient, self-explanatory experience when building or adjusting chatbot automation inputs.
NetBrain currently does not offer a self-service chatbot capability to guide users through pre- and post-validation steps during a network change. Validation today relies on manual execution or fully separate automation flows, without an interactive, transparent assistant to walk a user through each check. This enhancement would introduce a chatbot-driven validation flow that guides users step by step through pre-check and post-check tasks tied to a change, keeping each action visible and confirmable rather than relying on fully autonomous AI decision-making. Customers would benefit from faster, more consistent change validation while retaining the transparency and control needed to trust the automated process.
NetBrain currently applies self-healing remediation actions without distinguishing between edge devices and core infrastructure, so automated changes carry the same risk profile regardless of the affected device's role in the network. This enhancement would introduce configurable scope controls that let administrators limit fully automated self-healing to lower-risk, edge-level devices while requiring additional review, approval, or exclusion for core infrastructure changes. Customers would benefit from faster automated resolution of isolated, low-impact issues while reducing the risk of unintended, broad-impact changes to critical network infrastructure.
NetBrain currently cannot perform frequent, short-interval SNMP polling of interface data, such as polling every 30 seconds, which limits its ability to support real-time monitoring use cases. This enhancement would introduce configurable high-frequency SNMP polling for interface-level metrics, allowing intervals comparable to dedicated network monitoring platforms. Customers seeking to consolidate network visibility and real-time monitoring within a single platform would benefit from faster diagnostics, quicker issue resolution, and reduced reliance on separate monitoring tools.
Auto Remediation Manager currently supports only a limited set of built-in remediation intents and Configuration Templates, without direct access to the Golden Config template library. As a result, remediation workflows tied to config violations lack customization options and cannot leverage the broader set of templates already maintained in Golden Config. This enhancement would integrate Golden Config template access into Auto Remediation Manager, allowing customization of remediation actions using existing Golden Config data alongside built-in intents. Customers performing large-scale network changes would gain a more flexible and consistent remediation workflow, reducing the need to maintain duplicate templates across separate tools.
NetBrain currently does not provide a way to compare and validate firewall policy consistency across different vendor platforms. Enterprises operating heterogeneous firewall environments must manually reconcile differences in syntax, rule ordering, and behavior, such as ACL priority conflicts and inconsistent deny-by-default enforcement, which increases operational risk and compliance exposure. This enhancement would introduce a vendor-agnostic policy analysis capability that evaluates firewall configurations across platforms and flags inconsistencies or conflicts in security policy enforcement. Customers managing multi-vendor firewall estates would gain a unified view of policy alignment, reducing manual reconciliation effort and improving confidence in their overall security posture.
NetBrain currently does not provide clear guidance on which fields should be selected when configuring data export to certain ITSM tools, such as Jira, leaving customers uncertain about proper field mapping. This is inconsistent with tools like ServiceNow, where documentation on field selection is already available. This enhancement proposes extending field selection documentation and in-product guidance to cover each supported ITSM tool individually, clarifying that field requirements are specific to each integration. Customers configuring ITSM exports would benefit from reduced setup confusion and fewer support inquiries during integration configuration.
NetBrain currently allows users to view Layer 2 and Layer 3 connectivity but does not provide a way to visualize the physical rack layout of devices within a data center. This enhancement would introduce the ability to create and display rack diagrams, showing device position within a rack, potentially leveraging existing device location data or integration with external data sources for enrichment. Customers would benefit from improved infrastructure documentation and design accuracy, supporting reporting and planning activities that depend on understanding physical device placement.
The current Golden Assessment Library (GAL) is designed primarily for live network environments, and only a small portion of its intents apply to Playground because many rely on show commands that are not available offline. As a result, Playground users lack clear guidance on which assessments are actually usable in an offline context. This enhancement proposes a dedicated, streamlined version of the GAL library built specifically for Playground, presenting only the subset of intents supported in an offline setting. Customers using Playground for training, demonstration, or offline planning would benefit from a permanent, purpose-built resource that removes guesswork about which intents are applicable, improving usability and reducing confusion during offline sessions.
NetBrain currently requires users to complete the Import File Wizard and then separately navigate to the Manager or Benchmark to build Layer 2 topology, with no in-wizard guidance directing them to this next step. This disconnect makes the overall workflow feel unclear and increases the risk that users are unaware Layer 2 topology still needs to be built. This enhancement would integrate Layer 2 topology discovery earlier in the Wizard flow, or at minimum provide a direct in-wizard link prompting users to build Layer 2 topology immediately after import. Customers using the Import File Wizard would benefit from a more continuous, guided experience that reduces confusion and ensures topology data is complete without requiring separate manual navigation.
NetBrain's Import File Wizard does not currently provide users with an overview of its objective or the minimum information required before they begin the import process, which leaves users uncertain about what data to prepare, such as configuration files or topology layer details. This enhancement would introduce a home or introductory page displayed before the first step of the Wizard, outlining its purpose, listing minimum requirements, and providing helpful references such as hyperlinks to relevant commands. Customers new to the import process would benefit from clearer direction and reduced confusion, resulting in fewer setup errors and a smoother onboarding experience.
NetBrain currently requires users to manually build runbook templates and assessments after AI-driven knowledge documents identify a ticket type, even though the AI has already surfaced relevant troubleshooting insights. This enhancement would use AI-generated insights to automatically create partial runbook templates once a ticket type is identified, reducing the manual effort needed to translate those insights into an actionable runbook. Customers would benefit from faster runbook creation and reduced manual workload, particularly for common or recurring ticket types.
The incident portal currently lacks strong visual prominence within the interface, and customers are often uncertain whether maps refresh automatically or require manual regeneration. This enhancement would improve the visibility of the incident portal in the interface and provide clearer customer-facing documentation explaining key behaviors, including map refresh and update processes. Improved clarity would reduce customer confusion and support more confident, efficient use of the incident portal during troubleshooting.
Accessing Change runbooks today requires navigating through multiple UI steps, including locating relevant entries through ADT intent columns, which adds unnecessary complexity to a routine task. This enhancement would introduce a dashboard or simplified navigation path that allows users to locate and launch Change runbooks more directly, reducing the number of steps required. Customers performing batch remediation would benefit from faster access to runbooks and a more efficient overall workflow.
AI Ticket Analysis currently supports only CSV export of results, requiring customers to perform additional manual work to organize the data into a usable table format, such as ticket types with counts of repeated tickets. This enhancement would add a native tabular export option directly within AI Ticket Analysis, presenting results in a structured table format without requiring post-export manipulation. Customers reviewing recurring ticket trends would benefit from faster, more direct access to organized data, improving overall usability and reporting efficiency.
AI Ticket Analysis currently relies on the initial issue categorization assigned to a ticket, which may not accurately reflect the underlying root cause. For example, a ticket labeled as a routing protocol issue may actually originate from an unrelated device malfunction that triggered the observed symptoms. This enhancement would introduce AI-driven root cause analysis that reviews deeper diagnostic data to refine or reclassify ticket categorization, distinguishing primary causes from secondary effects. Customers would benefit from more accurate ticket categorization and faster identification of the true source of an issue, reducing time spent investigating symptoms rather than root causes.
AI Ticket Analysis currently does not offer reporting or dashboard functionality, leaving users unable to track trends over time or visualize how automation outcomes have evolved. Users have no built-in way to compare issue frequency across different time periods or to measure how automation efforts have matured. This enhancement would add reporting and dashboard capabilities directly within AI Ticket Analysis, supporting trend visualization and historical comparisons of ticket analysis results. It would also include visibility into automation hit rate, such as how frequently AI-suggested knowledge documents are actually used. Customers would gain the ability to measure automation maturity over time and identify shifting issue patterns without relying on manual data extraction.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.