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 does not currently provide a consolidated dashboard that aggregates usage statistics across automation asset types such as Network Intent and Qapp. Users must check each asset individually to determine how many times it has run and whether those runs succeeded or failed. This enhancement would add a dashboard that displays, for each automation asset, the total run count along with a breakdown of successful versus failed runs. Customers running automation at scale would gain a single view for tracking automation reliability and usage trends, reducing the manual effort required to compile this information from multiple sources.
NetBrain's Change module currently operates on a device-level automation model, requiring users to configure and apply changes on a per-device basis; there is no structured way to select a set of interfaces across multiple devices and treat that interface set as the target scope of a single bulk change task. This enhancement would allow users to select interfaces spanning one or more devices and apply the same configuration change to all selected interfaces within one change execution. Customers who need to apply common interface-level settings, such as enabling a specific security or spanning-tree feature, across large numbers of devices would benefit from reduced manual effort and more consistent, auditable change execution.
Network Intent alert email notifications currently use a fixed, non-configurable subject line, so recipients cannot determine which CI, Intent, or status code triggered an alert without opening the email body. This enhancement would allow the subject line to be customized using variables such as CI name, Intent name, and status code. Customers managing high volumes of alert emails would benefit from faster triage, since the subject line alone would convey enough context to prioritize review without opening each message.
The Change module currently executes commands in a continuous stream, offering only a fixed sleep delay or a send-enter step, with no mechanism to pause execution and require operator confirmation before proceeding to the next command. This enhancement would add an interactive pause point within Change module execution, allowing the operator to confirm, cancel, issue a custom command, or commit before continuing, along with an option to close the session. This capability would give operators greater control and oversight when running long or complex automation scripts against production devices, reducing the risk of unintended changes propagating without review.
NetBrain currently provides no way to associate a Change Runbook with the ServiceNow change or incident that originated it. Users must manually track and cross-link the two records, since the Change Management module does not prompt for or store a reference to the source ticket at creation time. This enhancement would prompt users, when creating a Change Runbook, to confirm or select the originating ServiceNow change or incident, and would maintain an automatic link back to that ticket throughout the runbook lifecycle. Customers using ServiceNow alongside NetBrain Change Management would benefit from reduced manual cross-linking effort and improved traceability between the two systems.
Automated Application Mapping currently has no way to schedule path runs at a recurring frequency with alerting on failure or change; this capability is only available through Benchmark, which requires collecting data across all or a specified set of devices first, making frequent runs impractical. This enhancement would add a standalone scheduler to Automated Application Mapping that executes path runs at a defined interval and triggers an alert when a run fails or the resulting path changes, without requiring the broader device data collection that Benchmark currently needs. Customers would gain the ability to monitor critical application paths more frequently and receive timely notification of failures or changes, improving responsiveness to path issues without the overhead of full data collection.
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 currently does not detect when a path's associated gateway has become invalid or stale, such as when the gateway reference was imported from a CSV file and no longer resolves correctly. When this occurs, the path calculation throws an exception and Path Browser/Path History simply displays N/A, giving no indication that an invalid gateway is the underlying cause. This enhancement would improve the path-handling logic to detect an invalid or stale gateway condition and either automatically re-resolve the gateway or clearly surface the invalid-gateway state to the user in Path Browser/Path History, rather than returning an unexplained N/A. Customers would benefit from faster root-cause identification and would avoid the manual workaround of forcing gateway re-resolution to restore path visibility.
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 Device Pane Properties Panel currently does not display any indication of benchmark task status or execution history for the selected device, requiring administrators to navigate to separate task management or history views to confirm whether benchmark data collection succeeded, failed, or is pending. This enhancement would surface benchmark task status directly within the Device Properties Panel, such as last run outcome and timing, so administrators can quickly verify data currency and task health without leaving the device context. Providing this visibility would reduce troubleshooting effort and improve confidence in device data accuracy during day-to-day network operations.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.