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.
Network Intent alert emails do not currently apply a consistent subject, greeting, or footer across the different diagnoses that trigger them, resulting in disjointed and inconsistent email presentation when multiple alerts are generated. This enhancement would introduce a common subject line, greeting, and footer (including a closing section such as regards and sender name) applied uniformly across all Network Intent alert emails, regardless of which diagnosis triggered the notification. Customers receiving Network Intent alerts would benefit from a consistent, professional, and easily recognizable email format, improving readability and reducing confusion when reviewing alerts from multiple diagnoses.
NetBrain currently requires an Associated Layout Style to be manually re-applied each time a Site Map is opened, even though documentation describes this association as functioning automatically. This limitation persists across common operations such as Site Rebuild, Recreate Site Map, and System Benchmark, requiring repeated manual intervention to restore the intended device positioning. This enhancement would cause an Associated Layout Style to automatically apply whenever its corresponding Site Map is opened, eliminating the need for a manual trigger. Automating this behavior would align product functionality with documented expectations and reduce repetitive manual effort for customers who rely on custom layout styles to maintain consistent map presentation.
NetBrain currently does not consistently apply a custom default map layout across all the ways a dynamic map can be created or opened. The layout applies correctly when devices are dragged onto a map from a site, but it does not apply when individual devices are dragged directly onto the map, and it does not automatically apply when a site map is simply opened. This enhancement would allow a custom layout, once set as the default, to apply automatically and consistently regardless of how devices are added or how the map is accessed, without requiring an extra manual step. Ensuring consistent behavior would reduce manual rework and provide a more predictable, reliable map presentation for customers who rely on standardized layouts across their environment.
NetBrain currently excludes end-user desktop devices from the bulk 'add to Device Group' action performed on the map, even when they are included in a multi-device selection alongside other device types such as switches. As a result, desktop devices must be added to a Device Group individually, one at a time. This enhancement would extend the map's multi-select add logic to include end-user desktop devices, allowing them to be added to a Device Group together with other selected device types in a single bulk action. Customers managing environments with mixed device types would benefit from a consistent, efficient workflow for building Device Groups without manual, one-by-one additions.
When performing live path calculation using CLI Command with Arguments, the system currently fails the path outright if no matching baseline data exists for that argument-based command, rather than falling back to the baseline route table. This enhancement would allow live path calculation to check the baseline route table when CLI Command with Arguments data is unavailable, instead of returning a failure. Customers relying on live path analysis would benefit from more resilient path calculation that continues to produce results even when argument-based baseline data has not yet been collected, reducing troubleshooting interruptions.
NetBrain currently does not provide a way to view or remove a manually set Fix-Up Gateway once it has been cached for path calculation. As a result, a one-time manual override can continue to be applied indefinitely, even after the underlying resolution issue no longer exists, with no UI-based way to clear it. This enhancement would add a UI option to view and delete previously cached Fix-Up Gateway entries, and would optionally allow a manually selected gateway to be applied one time without being saved to cache. Customers would gain better control over path calculation accuracy and avoid outdated manual overrides silently affecting future results.
NetBrain currently does not end a user session when the browser tab is closed; the session remains active until it separately times out. This means that reopening a stale tab or URL can present a confusing state rather than a normal login prompt. This enhancement would terminate the session automatically when the browser tab is closed, so that a later reopen leads directly to a clean login screen. Customers would benefit from clearer session behavior and reduced confusion when returning to the application after closing a tab.
The Function Portal does not currently provide a path for running Device Verification Tests live; DVT execution is only available in other parts of the platform. This enhancement would add the ability to execute DVT directly within the Function Portal interface. Customers who rely on the Function Portal for restricted or external access would be able to validate device state without needing to switch to a different tool or interface, improving efficiency for verification workflows.
NetBrain currently allows an L2 topology build to fall back to previously stored baseline data for a neighbor device when that device does not respond during a benchmark run, rather than reflecting that the device is offline or unreachable. This can result in the topology map retaining outdated links that no longer represent the actual network state. This enhancement would require current-run data to confirm a neighbor link before it is built or retained, and would skip topology construction for devices that did not respond in the current benchmark rather than defaulting to stale baseline data. Customers relying on topology maps for troubleshooting and network documentation would gain accurate, up-to-date visibility and avoid being misled by connections that no longer exist.
NetBrain currently does not provide an API to initiate a Network Intent or ADT run and retrieve its combined report or CSV output; running and exporting these reports today requires manual interaction through the UI. This enhancement proposes adding API endpoints that allow a Network Intent or ADT run to be triggered externally and its resulting report data retrieved programmatically, supporting scheduled and automated workflows. Customers who need recurring, hands-off reporting would benefit from reduced manual effort and the ability to integrate Network Intent results into external automation or reporting pipelines.
Network Intent Creation in auto mode currently enforces critical variables during device matching without exception, causing any device whose data does not align with those critical variables to be excluded from decoding and replication. There is no setting available today to relax this enforcement, which affects scenarios such as configuration drift checks where strict critical-variable matching is not desired and results in member Intents not being created for excluded devices. This enhancement would introduce an option to enable or disable critical-variable enforcement when running Network Intent Creation in auto mode. Customers would gain the flexibility to process and replicate devices that would otherwise be excluded due to critical-variable mismatches, improving coverage for use cases like configuration drift monitoring while preserving stricter matching where it remains desired.
NetBrain does not currently provide a mechanism to preserve a device's configuration and data when that device is deleted from the domain, resulting in permanent loss of historical information. This enhancement proposes adding an export hook that triggers automatically on device deletion, allowing the device's data to be exported elsewhere before removal, ideally through a customer-defined script such as Python. Customers would benefit from the ability to retain historical device records for compliance, auditing, or reference purposes without needing to manually capture data prior to deletion.
NetBrain currently does not provide clear documentation or a defined configuration workflow for connecting its GitHub SCM integration through a proxy server, leaving administrators uncertain how to set up or validate this connection, particularly after upgrades. This enhancement would introduce dedicated setup documentation and, where needed, an improved configuration workflow for establishing the GitHub SCM link via a proxy, along with confirmation that the integration operates reliably through a proxy on current NetBrain versions. Customers operating in proxy-restricted network environments would benefit from a documented, verified path to maintaining SCM connectivity without relying on trial-and-error configuration or support escalations.
When posting Network Intent results to a ServiceNow incident, the selection of which status codes get included is currently hardcoded to either all alert-level results or only the first success result, with no configuration option available. This enhancement would allow users to configure which Intent results are posted, such as selecting specific status codes or device-level results, rather than being limited to the two fixed options. Customers would gain the ability to tailor incident updates to the level of detail relevant to their support workflows, improving the usefulness and relevance of information surfaced in ServiceNow.
NetBrain currently displays the associated object-group name when searching by IP address for ASA firewalls, but this capability is not available for F5 or Palo Alto devices. This enhancement would extend the object-group-name display to IP-address search results for F5 and Palo Alto platforms, matching the existing ASA behavior. Customers managing mixed-vendor firewall environments would gain consistent visibility into object-group associations across platforms, reducing the need for manual cross-referencing during search and troubleshooting.
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.
NetBrain currently does not support discovery and mapping of AWS Cloud WAN, a managed wide-area networking service used to interconnect cloud and on-premises networks. This enhancement would add native discovery, modeling, and topology mapping capabilities for AWS Cloud WAN resources, consistent with existing support for other AWS networking constructs. Customers migrating from AWS Transit Gateway to Cloud WAN would gain complete visibility into their evolving network architecture without relying on manual workarounds.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.