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 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.
AI Ticket Analysis currently reports on recurring incidents, such as repeated circuit-down alerts, without the ability to drill down to identify the specific underlying source driving the recurrence. Users cannot determine which circuit, device, or application is most frequently associated with a given incident pattern directly within the analysis view. This enhancement would add drill-down functionality that traces a recurring incident category to its exact source, surfacing the most impacted device or a ranked list of associated devices. Providing this level of detail would help customers prioritize remediation efforts on the components driving the highest incident volume, reducing time spent manually correlating recurring alerts to root cause.
NetBrain currently does not provide a centralized library of best-practice guidance for common network change scenarios. Customers must rely on generic change templates without embedded rationale or standardized recommendations for well-known change types. This enhancement would introduce a Golden Change Library containing pre-built best-practice templates for common network change scenarios, including explanations of the underlying rationale, which customers could further customize and manage. Customers would benefit from consistent, guided change execution that reduces risk and improves quality without building this guidance from scratch.
AI Ticket Analysis currently requires users to manually gather and upload tickets for each customer account before analysis can be performed. This process becomes highly time-consuming for organizations managing many customer accounts on a single platform, as each account must be processed individually. This enhancement would introduce functionality to automate or schedule ticket imports directly from ITSM systems into AI Ticket Analysis, removing the need for manual gathering and uploading. Customers operating multi-tenant or managed service environments would benefit from continuous, streamlined ticket analysis across large numbers of accounts without repetitive manual effort.
NetBrain does not currently notify users when a feature, such as Layer 2 topology calculation, cannot function correctly because required underlying data has not been provided. This can leave users uncertain why a capability failed or produced incomplete results. This enhancement would introduce contextual system messaging that detects missing prerequisite data for a given feature and alerts the user before or during the attempted action, with guidance on what information is needed. Customers would gain clearer understanding of feature dependencies, reducing confusion and support inquiries related to unexplained functional gaps.
AI Ticket Analysis currently does not support direct export of ITSM ticket data to CSV format; only PDF export is available, requiring users to rely on XML or API-based JSON responses and manual conversion to obtain CSV output. This enhancement would add a native CSV export option for AI Ticket Analysis results, allowing ticket data to be extracted directly in a structured, spreadsheet-ready format. Customers would benefit from faster reporting and easier downstream data processing without needing manual conversion steps.
AI Ticket Analysis currently evaluates ticket volume based on frequency alone, without accounting for ticket priority. As a result, high-frequency but low-impact issues are treated the same as rare but high-priority incidents, obscuring the true business impact of recurring problems. This enhancement would add a priority-based breakdown to ticket analysis, categorizing results into high-frequency tickets and high-impact tickets based on priority level. Customers would benefit from more actionable insights that support better decision-making and automation planning by distinguishing between frequent low-impact issues and rare high-impact incidents.
AI Ticket Analysis currently requires AI to be enabled in order to derive insights from tickets, leaving no alternative path for customers who do not have AI enabled in their environment. This enhancement would introduce an offline, script-based alternative for ticket analysis, along with clearer enablement guidance, so customers can still perform ticket analysis and derive insights without relying on AI. Customers operating in environments where AI cannot be enabled would gain continued access to ticket analysis capability and value from the feature.
AI Ticket Analysis currently reports ticket volumes as aggregate counts only, without identifying which branch, application, or device each ticket is associated with. This limits visibility into where incidents are concentrated and how significant their operational impact is. This enhancement would extend AI Ticket Analysis to break down ticket data by branch, application, and device, allowing users to see not just how many tickets occurred but where and on what they occurred. Customers and their leadership teams would gain clearer visibility into the real business impact of recurring incidents, enabling more effective prioritization of remediation efforts.
Automation Insights currently displays intents and checks with labels that do not convey enough context, requiring users to open individual items to understand their purpose or to distinguish between similarly named entries, such as multiple instances of the same access list appearing across different devices. This makes it difficult to quickly identify relevant checks during troubleshooting or to determine whether repeated entries are distinct or duplicates. This enhancement proposes adding hover-over descriptions for each rule or check so users can understand its purpose without opening it, along with visual alert indicators on devices within the map view, such as a count badge showing the number of associated alerts. These additions would help users identify relevant automation resources and problem areas more quickly, reducing unnecessary navigation and improving efficiency during troubleshooting.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.