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 currently supports diagnostic checks based on CLI command output and parsed device data, but it cannot issue an API call to an external system and use the returned response as part of its diagnostic logic. This enhancement would extend Network Intent to support API-based calls as a step within an intent, allowing the returned data to be evaluated and incorporated into the overall diagnostic assessment. Customers integrating with external systems, such as monitoring platforms or ticketing tools, would gain a more complete and automated diagnostic workflow without needing to build custom logic outside of Network Intent.
Summary Dashboards currently aggregate device data at the site level but do not provide a way to select or exclude individual devices within that aggregated view. Users who want to focus on a subset of devices at a site must rely on the full aggregate result, with no mechanism to narrow the displayed devices. This enhancement would add a device selection filter, such as a checkbox list, to site-level summarization widgets so users can choose which devices to include in the displayed results. This would give customers more granular control over site-level reporting, allowing them to focus on relevant devices without needing to build separate dashboard configurations.
When multiple Seed Network Intent instances generate CSV export files, the system currently assigns generic default suffixes such as (1) and (2) to distinguish files, rather than identifying them by device name. This makes it difficult for users to determine which exported file corresponds to which device without opening each file individually. This enhancement proposes allowing users to customize the export file naming convention so that the device name, rather than a generic numeric suffix, is used to differentiate CSV files generated by each Seed Network Intent instance. Customers managing environments with a large number of Seed Network Intents would benefit from being able to quickly identify and organize exported reports without manually opening files to determine their source device.
NetBrain currently displays the underlying database name, rather than the configured domain name, in report notifications generated by QApp. This can create confusion for administrators who manage multiple domains, since the notification does not reflect the domain's intended identity. This enhancement proposes that QApp report notifications reference the domain's display name instead of its internal database identifier. Ensuring accurate domain labeling in these notifications would reduce confusion and support overhead for customers operating multi-domain environments.
NetBrain currently does not support discovery, modeling, or mapping of OpenStack environments. This enhancement would add native discovery and topology mapping capabilities for OpenStack-based infrastructure, consistent with existing support for other virtualization and cloud platforms. Customers adopting OpenStack as part of their hypervisor strategy would gain visibility into their network infrastructure without relying on manual workarounds.
The Interface Report currently does not provide a way to sort interfaces in a defined order within the table view. This enhancement would add sorting controls to the Interface Report so that interfaces can be arranged by a selected order, such as interface name or index. Customers reviewing large interface lists would benefit from improved readability and faster identification of specific interfaces during audits and troubleshooting.
NetBrain's Ansible integration currently supports only Cisco ACI natively within the Integrated Edition framework, which prevents other technologies, such as Meraki, from being properly onboarded through the Ansible Agent. As a result, customers seeking to use Ansible for additional vendor platforms must rely on unsupported manual workarounds, including storing credentials in plain text within UI fields, rather than using a secure, natively supported integration path. This enhancement proposes extending the Integrated Edition framework so that the Ansible Agent can support a broader range of device technologies beyond Cisco ACI, including secure handling of credentials and configuration for each supported technology. Broadening this framework would allow customers to extend their existing Ansible automation investment to additional vendor environments without resorting to insecure or unsupported workarounds, improving both security posture and integration coverage.
NetBrain currently does not provide a way to organize paths within an application into sub-groupings based on location or market. This enhancement would allow paths under a given application to be categorized and displayed under location-specific groupings, such as by market or region. Customers managing applications that span multiple geographic areas would benefit from improved organization and faster navigation when working with large sets of paths.
NetBrain currently provides only a single configuration field, the CLI Command to Connect, for jump server (jumpbox) setups. This field is used to define the command for connecting from the jumpbox to target devices, but there is no separate mechanism to configure or optimize the connection between the NetBrain Front Server and the jumpbox itself, such as enabling SSH tunnel multiplexing to avoid establishing a new tunnel for every backend connection. This enhancement would introduce a distinct configuration section, for example within the Advanced tab of jumpbox definitions, dedicated to Front Server-to-jumpbox connection parameters. This section would support SSH multiplexing options such as control master and control path settings, allowing a single tunnel to be reused across multiple backend sessions. Customers using jump servers at scale would benefit from reduced resource consumption on both the Front Server and the jumpbox, since a persistent multiplexed tunnel avoids the overhead of establishing a full SSH tunnel for every device connection.
NetBrain Change Management currently does not provide a way to change the order in which devices are processed within a change task. Devices are executed in a fixed sequence determined at task creation, with no option to rearrange them afterward. This enhancement would allow users to reorder devices within a Change Management task, such as through drag-and-drop or an explicit sequencing control, before or during execution. Supporting flexible device ordering would help customers manage dependencies between devices and align execution sequence with their operational change requirements, reducing manual workarounds and risk during network changes.
NetBrain Change Management currently does not support connecting to an external Git repository to store, version, or synchronize Configuration Templates. Teams that already maintain their templates in a source control system must manage them separately and manually reconcile changes between the external repository and NetBrain. This enhancement would allow Change Management to integrate with an external Git repository via API, enabling templates to be pulled from, and optionally pushed to, that repository directly within NetBrain. This would give customers a single source of truth for configuration templates, improve version tracking, and reduce manual effort in keeping templates synchronized across systems.
NetBrain currently does not provide a folder structure for organizing Configuration Templates, limiting users to a flat list as the number of templates grows. This enhancement would allow users to create, rename, delete, and nest folders and subfolders to organize Configuration Templates, similar to a standard file system hierarchy. Customers managing a large number of templates would benefit from improved organization and faster navigation when locating and maintaining specific templates.
NetBrain Runbooks currently do not support merging two branches back into a single branch once a process has split into parallel paths. This enhancement would introduce a merge node or equivalent mechanism that allows separate branches to converge into one continuation point within the same Runbook. Customers designing complex workflows with conditional or parallel branching would benefit from more accurate representation of their operational processes and reduced need for duplicating downstream steps across branches.
NetBrain currently limits the stencil drawing tool to a single connection line between any two devices or sites on a map, so users cannot represent more than one physical interface or link between the same pair of endpoints. This enhancement would allow multiple stencil lines to be drawn between the same two devices or sites, with each line representing a distinct interface. Supporting this capability would let customers accurately depict network topologies that include multiple parallel links, improving map accuracy for capacity planning and troubleshooting.
NetBrain currently requires LDAP/AD synchronization to be triggered manually, with no option to configure it to run automatically on a recurring basis. This enhancement would add a scheduling capability allowing administrators to set LDAP/AD sync to occur automatically at defined intervals, such as daily. Customers managing user accounts through centralized directory services would benefit from reduced administrative overhead and more consistent alignment between NetBrain user records and their source directory.
The Device Raw Data API endpoint currently returns only data captured in the current baseline and cannot retrieve data that falls outside of that baseline snapshot. This limits automated workflows that require access to historical or on-demand device data collected independently of the baseline refresh cycle. This enhancement would extend the API to support triggering a live or on-demand data collection from the device, allowing retrieval of data not present in the current baseline. Customers relying on automation and integrations would benefit from more complete and timely device data access, reducing dependency on baseline refresh timing for accurate reporting and diagnostics.
NetBrain currently does not alert a Network Change Approver when a Config Change node lacks corresponding Rollback commands, leaving approvers without a clear indication of incomplete change definitions. This enhancement would display a warning icon on the Rollback tab whenever configuration commands exist without matching rollback commands. Providing this visual cue would help approvers make more informed decisions and reduce the risk of approving changes that cannot be safely reverted.
NetBrain path calculation currently returns only the single best-matching path when multiple valid paths exist for a given source and destination in MPLS environments, limiting visibility into alternate or equal-cost routes. This enhancement would extend path calculation to identify and display all possible paths that satisfy the calculation criteria, rather than resolving to one best match. Customers operating MPLS networks would gain complete visibility into candidate routing paths, improving confidence in troubleshooting and reducing the need for manual verification of alternate routes outside the tool.
NetBrain container site maps do not currently display the devices and connections belonging to sub-sites and leaf sites; users must navigate into each individual site map to view that detail. This enhancement would automatically render all sub-site and leaf site devices on the container map, along with the connections between sites, and include interface and IP address details on those connections. Customers would benefit from a single consolidated view that makes it easier to locate a device and understand connectivity across sites without opening multiple maps.
When a scheduled Discovery or Benchmark task is configured with device scope set to a Device Group, the Task Management screen currently displays 'N/A' in the device scope column instead of the selected group name, leaving administrators unable to confirm which scope was actually applied to the task. This enhancement would update the Task Management view to display the actual Device Group name (or other selected scope type) for scheduled Discovery and Benchmark tasks. Providing this visibility would allow administrators to verify scheduled task configurations are correct without needing to reopen or re-edit the task definition, reducing uncertainty and troubleshooting effort for scheduled discovery operations.
NetBrain currently experiences significant lag and reduced responsiveness when rendering maps containing a large number of devices, particularly beyond several hundred nodes, limiting usability for customers managing large network topologies. This enhancement would introduce performance improvements to the map rendering engine, such as progressive or level-of-detail rendering, along with documented sizing and configuration guidance to help customers optimize performance for large maps. This would allow customers with extensive network environments to work efficiently with large-scale topology maps without experiencing unresponsiveness.
Service Monitor currently provides resource usage monitoring, such as disk usage tracking, for database servers, but does not extend this capability to Windows servers. As a result, administrators lack visibility into resource consumption trends and potential capacity issues on Windows-based infrastructure. This enhancement would add resource usage monitoring for Windows servers within Service Monitor, including metrics such as disk usage, with configurable alert thresholds to notify administrators when usage exceeds acceptable levels. Extending this monitoring capability would give customers consistent visibility across their server infrastructure and allow them to proactively address resource constraints before they impact system performance or availability.
NetBrain currently requires manual steps to initiate auto-remediation actions, and there is no defined mechanism to trigger pre-approved remediation through a single API call or one-click action. In addition, auto-remediation workflows have not been validated or optimized for execution across very large device populations. This enhancement would introduce a zero-touch remediation trigger, allowing pre-approved changes to be initiated via API or a single click without additional manual intervention, and would ensure auto-remediation can be reliably executed at scale across networks of up to 15,000 nodes. Customers operating large, complex network environments would benefit from faster, more consistent remediation with reduced operational overhead and improved confidence in automation at enterprise scale.
NetBrain currently does not provide a way to perform bulk Telnet/SSH and Privilege credential updates across a domain without the CLI/SNMP settings lock re-engaging during the tuning process, which interrupts the update workflow for administrators managing periodic credential rotation policies. This enhancement would introduce an option to temporarily suspend or bypass the automatic re-locking of Shared Device Settings while a bulk credential update or tuning operation is in progress, then restore the lock state once the operation completes. Customers subject to recurring credential rotation requirements, such as periodic security policy updates, would benefit from a reliable bulk update process that does not require repeated manual unlocking of each device.
NetBrain currently restricts the number of neighbors that can be added to a topology map in a single operation to 50, which requires customers with larger environments to perform repeated manual actions to complete their topology. This enhancement would introduce a configurable or increased neighbor limit, allowing more neighbors to be added in a single pass during map expansion. Customers managing large-scale networks would benefit from reduced manual effort and faster topology completion when building out maps.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.