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.
In the Intent diagnosis view, Compare and Diagnosis Details operate as independent features, with Compare always showing current output versus a fixed baseline regardless of the diagnosis logic defined. The current interface does not communicate this separation, leading users to assume the two features reference the same underlying data. This enhancement would add a GUI indicator, such as a tooltip or inline hint, clarifying that Compare and Diagnosis Details function independently and explaining how Compare's baseline comparison relates to the diagnosis logic. Providing this clarity would reduce user confusion and support inquiries related to misinterpreting the relationship between these two features.
NetBrain's webhook follow-up action currently requires users to manually base64 encode their username and password before entering the combined string into the Authorization header when configuring Basic Authentication. This manual step introduces the risk of formatting errors and requires customers to perform the encoding outside of NetBrain using external tools. This enhancement would allow NetBrain to accept a plain username and password for Basic Authentication and automatically perform the base64 encoding internally before constructing the Authorization header. Customers with security requirements around credential handling would benefit from a more streamlined and less error-prone configuration process when setting up webhook integrations.
The CVE Report currently does not provide a way to mark individual CVE entries as verified or invalid, nor does it support adding comments directly within the report. As a result, reviewers must export the data and track verification status and notes outside of NetBrain. This enhancement would add two columns to the CVE Report: a Verify/Invalid status field and a free-text Comments field, allowing users to annotate each CVE entry in place. Customers responsible for vulnerability review would benefit from a streamlined workflow that eliminates manual export and external tracking, improving efficiency and accuracy of CVE assessment reviews.
NetBrain does not currently provide a way to reserve IP addresses for planned or future use, unlike dedicated IPAM solutions that offer this capability. This enhancement would introduce an IP address reservation feature, allowing administrators to mark specific addresses or ranges as reserved before they are assigned to a device. Customers who rely on NetBrain alongside or in place of separate IPAM tools would benefit from consolidated address planning, reduced risk of address conflicts, and improved visibility into available address space during network changes.
NetBrain currently has no automated way to convert a benchmark task failure, such as a device or CI failing to back up configuration, NDP table, route table, ARP table, MAC table, STP table, device info, or interface info, into a trackable remediation action; support staff must manually review benchmark alert emails and create tickets themselves. This enhancement would extend the existing ServiceNow alert integration so that a benchmark run reporting a device backup failure automatically generates a ServiceNow ticket for remediation, leveraging the existing OAuth-based connection and alert plugin. Customers relying on ServiceNow for operational workflows would benefit from faster identification and tracking of backup failures, reducing manual monitoring effort and improving remediation turnaround time.
Today, generating a remediation script for configurations that aggregate multiple protocols requires manual identification of the correct parent class-map and policy-map structures before a modification can be applied. This process is error-prone because a single configuration may contain multiple protocol-specific class-map and policy-map sections, making it difficult to reliably determine which parent structure a given change belongs to. This enhancement would improve remediation script generation to automatically and accurately identify the correct parent class-map and policy-map structure for a requested modification, such as removing a specific match statement under the correct class or updating a priority statement under the correct policy-map and class combination. Customers managing complex, multi-protocol configurations would benefit from more accurate automated remediation, reduced manual review, and lower risk of applying changes to the wrong configuration section.
The Observability Dashboard currently has no dedicated view for AAM path intents that consolidates a path and its associated follow-up diagnosis checks, such as Ping Response or Routing Next Hop verifications, into a single entry. When using the existing Intent Dashboard filtered to path-based intents, each follow-up check appears as a separate entry rather than being grouped under its parent path, creating confusion when assessing path health. This enhancement would introduce a dedicated Observability Dashboard view for AAM paths that displays one consolidated entry per path intent, incorporating success or alert status derived from all related diagnosis checks. Customers monitoring critical paths would gain a clearer, continuous assessment view without needing to manually correlate separate entries for the same path.
Dashboards currently display only the results of the most recent run, with no option to filter by a broader time range or to view how results have changed over time. This enhancement would introduce built-in time range filters, such as Last Hour, Last 24h, and Last 7 Days, along with a trend visualization capability at the dashboard level. Customers would gain the ability to review historical performance and identify patterns over time, improving visibility into operational trends without relying on manual comparison of individual runs.
NetBrain's current self-healing workflow allows external systems to trigger remediation through a Network Intent that generates a Change Management runbook, but it does not support triggering a troubleshooting runbook—consisting of a diagnostic sequence of CLI and Network Intent nodes—directly from a ticketing system, nor does it return a summarized result back to the originating record. This enhancement would extend the Triggered Automation Framework to allow a ServiceNow ticket to invoke a troubleshooting runbook, automatically targeting devices at a specified site, and to post a summarized diagnostic result back to the incident. Customers using ServiceNow for incident management would benefit from faster triage and reduced manual effort, since diagnostic context would be available directly within the ticket without requiring a separate remediation workflow.
NetBrain currently requires a full seat license for any user to view AI Co-Pilot or Chatbot generated insights, even when that user only needs read-only access to the portal for insight consumption rather than full platform functionality. This limitation prevents organizations from extending AI-driven insights to a broader set of stakeholders without incurring additional licensing costs. This enhancement would introduce a lightweight or restricted access mode that allows users to view AI Chatbot insights through the customer portal without requiring a full seat license. Customers with large teams or occasional viewers would benefit from wider visibility into AI-driven insights while managing licensing costs more efficiently.
NetBrain currently does not provide a way to convert a manually established Fix-Up link into a native L2 border link within ACI-Switch topology, leaving such links classified differently from natively calculated L2 border links even after the connection has been validated. This enhancement would add the capability to convert a Fix-Up link to an L2 border link, allowing the corrected connection to be represented consistently with other calculated fabric links. Customers operating ACI environments would benefit from more accurate topology representation and reduced manual link maintenance during troubleshooting and documentation.
NetBrain discovery does not consistently identify all VPN tunnels for SD-WAN devices from certain vendors, which can leave some devices unreachable for CLI-based access even though they are configured with valid credentials. This enhancement would extend discovery to use the vendor's REST API to retrieve tunnel and device relationship data directly from the SD-WAN controller, filling gaps left by traditional discovery methods. Customers running SD-WAN environments would gain more complete and reliable topology and device visibility, reducing troubleshooting delays caused by incomplete discovery.
NetBrain's Golden Engineering Studio currently requires configuration standards to be entered manually, with no direct integration to external documentation platforms such as Confluence where these standards are often authored and maintained. This enhancement would introduce an API-based integration that automatically imports configuration standards from Confluence into GES, keeping standards synchronized without manual re-entry. Customers who maintain configuration governance documentation in Confluence would benefit from reduced administrative effort and improved consistency between documented standards and enforced GES rules.
Change Analysis Reports currently display changed configuration values without clearly indicating the specific interface or object each change applies to, leaving users to manually correlate the value with its source. This enhancement would update the report to associate each detected change with its corresponding interface or object, presenting the two together in the same report entry. Customers reviewing configuration changes would benefit from faster root-cause identification and reduced manual cross-referencing during audits and troubleshooting.
Today, the Document node within a Runbook must be manually triggered each time to generate and save the resulting Word document, requiring user intervention at every execution. This enhancement would allow the Document node to automatically execute and save the generated document to a specified location as part of the Runbook run, without requiring a manual step. Customers running Runbooks on a recurring or scheduled basis would benefit from consistent, hands-free documentation generation, reducing manual effort and the risk of missed or delayed document creation.
NetBrain currently displays Diagnosis result messages in full within the ServiceNow ticket integration tab, regardless of message length, which can present more detail than some support tiers require at a glance. This enhancement would allow long diagnosis messages to be collapsed by default within the ServiceNow tab, with an option to expand and view full details on demand. Providing this control would help support teams, particularly L1 NOC staff, review ticket information more efficiently without being overwhelmed by lengthy diagnostic text.
NetBrain's current Data View logic for Interface Highlight and Data Unit forces display of interfaces that do not belong to the active map, and triggering AutoNI can disrupt a user's existing map layout as a result. This enhancement would make the Highlight and Draw Interface logic configurable so that interface display behavior can be controlled and does not override or alter a map the user has already built. Providing this control would give customers predictable map behavior when running Network Intents and AutoNI, preventing unintended disruption to existing topology views.
NetBrain currently limits the map view to displaying a maximum of four entries per intent result, requiring users to click an additional menu to see remaining entries when more results exist. This enhancement would introduce a configurable setting to increase the default number of entries shown on the map. Customers running diagnostic or compliance checks with larger result sets would gain immediate visibility into complete output without extra manual steps, improving efficiency during troubleshooting and validation workflows.
For Network Intents built using an API Parser, replication currently follows the traditional device-scope model rather than accounting for the devices actually managed through API Server Manager. This enhancement would extend replication logic so that the scope of an integrated Network Intent is determined by the Managed Devices configured in API Server Manager. Aligning replication scope with the API-managed device list would ensure intents replicate correctly to the devices the API Parser applies to, reducing gaps or mismatches for customers relying on API-based integrations.
NetBrain currently does not support organizing Network Change records into custom subfolders, requiring users to manage all changes within a single flat list regardless of site, equipment type, or status. This enhancement would allow users with appropriate permissions to create, rename, and manage custom subfolders, and to move Network Changes between them for organizational purposes. Customers managing a high volume of network changes would benefit from faster navigation and clearer categorization of active, completed, and test changes.
NetBrain currently measures only the time required to complete data collection from a device, without capturing the network latency between the Front Server and that device. This enhancement would add latency as a collected metric during each data collection cycle, alongside existing timing data. Providing this visibility would help administrators distinguish between slow data collection caused by device processing versus network latency, supporting faster troubleshooting and more accurate performance monitoring.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.