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 requires Azure and AWS discovery and benchmarking credentials to be stored directly within the platform, with no option to retrieve them from an external secrets management system. This enhancement would add support for integrating with HashiCorp Vault so that discovery and benchmarking credentials can be pulled dynamically from Vault rather than stored locally, along with configuration documentation for administrators. Customers with strict credential management policies would benefit from centralized secrets governance, reduced credential sprawl, and improved security posture across their cloud discovery workflows.
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.
NetBrain currently manages API-driven integrations, such as techspec/adapter scripts, third-party API adapters, and native REST endpoints, independently of one another, with no centralized layer for policy enforcement, traffic control, or observability across them. Administrators must configure and monitor each integration point separately, which limits consistent security controls and visibility into overall API traffic and performance. This enhancement would introduce a native API Gateway or API Management module with a centralized GUI to configure, monitor, and audit API traffic, including policy templates for rate limiting and caching, security controls such as authentication and IP allow/block lists, resilience mechanisms for isolating failed requests, and observability features such as correlation-ID tracing, log viewing, and alerting on error-rate spikes. Customers managing large-scale, multi-source API integrations would benefit from consistent policy enforcement, improved security posture, and faster troubleshooting through unified traffic visibility.
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 does not display the available or remaining license count on the License tab for accounts using the Universal license model, even though this count is shown for other license models. This enhancement would extend the available-license-count display to the Universal license model so that remaining capacity is visible consistent with other license types. Customers on the Universal license model would gain the same license capacity visibility available to other license models, supporting more accurate planning and reducing uncertainty about remaining license availability.
NetBrain currently requires a Network Intent Template to be decoded, through IBNA or ADT, before it can be used under Auto Intent. This decode step must be repeated whenever devices are added to or removed from the associated device set, creating recurring manual effort. This enhancement would allow a Network Intent Template to be used directly under Auto Intent on an on-demand basis, without requiring an initial decode or subsequent re-decode when the device set changes. Customers managing dynamic device inventories would benefit from reduced setup and maintenance time, since automation would no longer depend on repeated decode operations to stay current.
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 currently requires Usage Reports to be generated and distributed manually, with no option to schedule recurring generation or automatic email delivery. This enhancement would add a scheduling capability for Usage Reports, allowing users to configure recurring runs, such as weekly or monthly, with results automatically emailed to designated recipients. Customers who rely on regular usage reporting for stakeholder visibility would benefit from reduced manual effort and more consistent, timely distribution of report data.
NetBrain currently does not notify administrators when a user is unable to log in because the seat license limit has already been reached. Administrators only learn of the issue after the fact, typically when the affected user reports the problem. This enhancement would add an email notification triggered at the moment a login attempt fails due to insufficient seat licenses, sent to a designated administrator mailbox. Customers would gain immediate, proactive awareness of license capacity issues affecting active users, reducing downtime and reliance on manual reporting.
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.
NetBrain's pre/post configuration comparison currently evaluates the masked or displayed value of sensitive fields rather than the underlying data, so a change to a hashed-out field appears identical across snapshots and is reported as no change. This same limitation affects configuration restoration and export, since a masked value cannot be meaningfully copied back to a device. This enhancement would allow comparison, restoration, and export processes to detect that the underlying value of a masked sensitive field has changed by comparing a hash or fingerprint of that value, while continuing to display the field as masked to the user. Customers would gain accurate change detection and reliable restoration behavior for sensitive fields without compromising the security benefit of masking.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.