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 does not provide a way to disable an individual Diagnosis definition while keeping its configuration intact for future use; the only available workaround is to duplicate the Diagnosis and modify the copy, which is not practical when replication is configured against the original. This enhancement would add an enable/disable toggle at the Diagnosis level, allowing a Diagnosis to be turned off without deleting it or losing its settings. Customers managing multiple similar Diagnoses, especially those with dependent replication, would benefit from a simpler way to temporarily deactivate and later reactivate a Diagnosis without duplicating effort.
NetBrain currently requires a full server-based deployment to access its network mapping, pathing, change tracking, and health-check capabilities, which may not be practical for smaller teams or individual engineers with limited budget or infrastructure. This enhancement proposes a lightweight, standalone toolset that could run locally on a desktop or laptop without requiring a server, offering a subset of core functionality such as mapping, pathing, change detection, and health checks, while excluding intents, QApps, and automation features. Providing this streamlined option would allow network, security, and cloud engineers in smaller organizations to benefit from key diagnostic and visualization tools on demand, expanding NetBrain's reach to teams that cannot adopt the full platform.
NetBrain currently does not support installation or operation on Rocky Linux 9, limiting deployment options to the currently validated operating systems. This enhancement would extend NetBrain server installation and runtime support to include Rocky Linux 9 as a validated operating system. Customers standardizing their infrastructure on Rocky Linux would be able to deploy NetBrain without requiring an alternate operating system or workaround configurations.
NetBrain currently does not propagate a password update made in Network Settings to devices that are already configured with the corresponding shared credential, requiring administrators to manually update the password on each affected device. This enhancement would automatically synchronize the updated credential across all devices associated with that shared credential profile as soon as it is changed in Network Settings. Customers subject to periodic password rotation policies would avoid authentication failures and account lockouts caused by devices continuing to use outdated credentials after a manual update.
NetBrain currently does not display the Published service target type within the VPN PSC Endpoint NCT Table, limiting visibility into this endpoint attribute during analysis. This enhancement proposes adding a column to surface the Published service target type directly in the NCT Table for VPN PSC Endpoints. Customers managing cloud VPN environments would gain more complete endpoint context without needing to reference separate tools or configurations.
NetBrain does not currently offer a native or certified adapter for integrating with ManageEngine OPManager, a widely used network monitoring platform. This enhancement would add a supported integration that allows NetBrain to exchange device and monitoring data with OPManager, such as pulling end-system details or cross-referencing discovered devices. Customers running OPManager alongside NetBrain would benefit from consolidated visibility and reduced manual effort in correlating data between the two platforms.
NetBrain currently opens a separate SSH session for each CLI command task performed against a device, including sessions triggered by Network Intent, Runbook execution, and other live data retrieval operations. This results in multiple concurrent or sequential SSH connections being established to the same device for what could be handled through a single session. This enhancement would have NetBrain establish and reuse one SSH session per device across these CLI-driven tasks, rather than opening a new session for each task type. Customers would benefit from reduced login overhead on network devices, lower risk of hitting device session limits, and more efficient CLI-based data retrieval overall.
NetBrain does not currently provide an audit trail that identifies which user added, deleted, or modified a device record within the device inventory. As a result, administrators have no reliable way to trace how a previously removed device reappeared in the system, which can create confusion when reconciling inventory against external systems such as a CMDB. This enhancement would add audit log entries that capture the user, action type, and timestamp for each device addition, deletion, or modification. Administrators would gain clear visibility into inventory-level changes, supporting faster root-cause analysis and more accurate reconciliation with external systems of record.
NetBrain currently does not support discovery and mapping of Google Cloud VMware Engine (GCVE) environments. This enhancement would add native discovery, modeling, and topology mapping capabilities for GCVE resources, consistent with existing public cloud support. Customers running VMware workloads on Google Cloud would gain complete visibility into their hybrid and multi-cloud infrastructure without relying on manual workarounds.
NetBrain currently does not provide a way to identify which version of the Smart CLI client each user has installed, leaving administrators without visibility into client version distribution across their organization. This enhancement would introduce a report or tracking view listing users along with their currently installed Smart CLI client version. Having this visibility would help administrators plan upgrades in advance, particularly in environments where users lack administrative rights to install or update the client independently, and where new releases require a minimum client version.
NetBrain currently does not provide validated support for installing or operating on Rocky Linux, which limits customers who need to move off CentOS as it approaches end of support. This enhancement would extend NetBrain server installation and runtime support to include Rocky Linux as a supported operating system, along with documented guidance for migrating an existing database and deployment from CentOS to Rocky Linux. Customers modernizing their infrastructure would be able to complete the operating system transition without disrupting their existing NetBrain environment.
NetBrain currently allows Inventory Reports to be generated and exported manually, but does not provide an option to schedule recurring generation with automatic email delivery. This enhancement would add a scheduling capability for Inventory Reports, allowing users to configure recurring runs (such as daily or weekly) with results automatically emailed to designated recipients. Customers who rely on Inventory Reports for ongoing asset and compliance tracking would benefit from reduced manual effort and more consistent access to up-to-date data.
Service Monitor currently does not provide a way to track RabbitMQ pending message counts or notify administrators when queue backlog exceeds an acceptable level. This enhancement would add a configurable threshold for RabbitMQ pending messages within Service Monitor, along with automated notifications when the threshold is exceeded. Customers would gain earlier visibility into message processing backlogs, allowing them to address underlying issues before they impact system performance or availability.
NetBrain currently does not support discovery of Azure Operator Nexus (Carrier-Grade Infrastructure), a newer Azure service used to host carrier network functions in the cloud. This enhancement would add the ability to discover and map Operator Nexus node types, topologies (such as L2, L3, and overlay), and traffic types (including unicast, multicast, and high-availability paths). Customers operating carrier-grade workloads in Azure would gain full visibility into their hosted services alongside existing Azure cloud infrastructure already modeled in NetBrain.
NetBrain's Benchmark results currently list devices in the 'Devices with retrieval failures' table when certain commands fail during data retrieval, even if those commands are only applicable in a global context or a specific VDOM and the overall retrieval status shows succeeded. This creates confusion, as customers see devices flagged as failures without a clear indication that the underlying data was retrieved successfully. This enhancement would refine command scoping logic for multi-VDOM firewalls so that VDOM-specific or global-only commands are correctly evaluated per context, and would exclude devices from the failure table when no genuine retrieval or processing issue exists. Providing accurate failure reporting would reduce unnecessary investigation effort and improve customer confidence in Benchmark results for multi-vendor, multi-VDOM environments.
NetBrain's QApp Python scripting environment currently has no built-in method for a script to write its output directly into the platform's Public or Private file folders; any generated files must be handled and stored outside of NetBrain. This enhancement proposes adding a Python API function within the QApp scripting context that allows a script to save output files directly to a specified Public or Private folder. This would let customers persist automation output within NetBrain for future reference and reuse without relying on manual file transfer steps.
Custom DNS server settings configured for the OneIP Table are currently applied and executed only from the NetBrain core server, which in some customer environments does not have network connectivity to the designated DNS server. This limitation prevents hostname resolution from completing successfully even though a Front Server in the same environment does have the required connectivity. This enhancement proposes allowing the custom DNS server configuration and associated resolution calls for the OneIP Table to be executed from the Front Server instead of the core server. Customers whose DNS infrastructure is only reachable from the Front Server would gain accurate hostname resolution for unknown entries without requiring additional network changes or workarounds.
NetBrain currently stores Telnet/SSH credential values directly with each device record rather than maintaining a live reference to the credential definition. As a result, when a credential is deleted from Network Settings, devices that were assigned that credential retain the stale username and password values, and administrators have no way to identify which devices are affected. This enhancement would introduce a report or search capability that identifies all devices currently assigned a credential that no longer exists in Network Settings. Customers would benefit from the ability to proactively locate and remediate devices with orphaned credential assignments, improving credential hygiene and reducing the risk of failed or unauthorized access attempts.
Custom reports currently stop generating once output reaches 100,000 lines, preventing users from viewing or exporting complete results when the underlying data set is larger. This enhancement would make the report line limit configurable, allowing administrators to raise the threshold to accommodate larger data sets. Customers working with large-scale environments would benefit from complete, accurate reporting without truncation or the need for manual workarounds to piece together full results.
NetBrain currently allows Inventory Reports to be generated and exported manually, but there is no option to schedule recurring report generation or have the results automatically delivered by email. This enhancement would add a scheduling capability for Inventory Reports, allowing users to configure a report to run on a recurring basis, such as quarterly, and be automatically emailed to designated recipients. This would support audit and compliance workflows by providing a reliable, time-stamped record of report delivery without requiring manual export or screenshot capture.
NetBrain currently applies a fixed default protocol (IPv4 with UDP/TCP) for path calculation, and this default applies uniformly to all users without any administrative control over it. This can produce results that are misleading when a policy match is evaluated against a protocol that does not reflect the traffic type the user actually intends to analyze. This enhancement would allow administrators to configure the default protocol and port used for path calculation, such as ICMP or TCP on port 443, so that the system-wide default better reflects common troubleshooting scenarios. Customers would gain more accurate and predictable path calculation results out of the box, reducing confusion around policy match outcomes and the need for users to manually adjust protocol settings on each path calculation.
NetBrain currently displays a protocol label in path trace denial results that does not accurately reflect the underlying evaluation logic. When IPv4 is selected without specifying a transport protocol, the path denial message states that the path was denied by a matched TCP/UDP policy, even though no specific transport protocol was actually evaluated or matched. This enhancement would correct the displayed wording to accurately represent the matching logic used, such as labeling the result as IP-based or indicating that any protocol is permitted when no specific transport protocol is selected. Accurate labeling would help customers correctly interpret path trace results and avoid misdiagnosing policy behavior during troubleshooting.
NetBrain currently requires manual initiation of subnet scans and does not support automatic, recurring discovery against a defined list of subnets. It also has no mechanism to automatically remove devices from inventory when they become unreachable for an extended period. This enhancement would allow administrators to configure a list of subnets for automatic, scheduled scanning, so that any new device responding with valid SNMP configuration is automatically added to inventory. It would also add a configurable time threshold after which a device on a monitored subnet that remains unreachable is automatically removed from inventory. Customers managing large or dynamic environments would benefit from reduced manual inventory upkeep and more accurate, self-maintaining device records.
NetBrain currently renders SD-WAN connectivity between nodes as a full mesh of individual tunnel links on topology maps, which can make maps with many SD-WAN edge devices difficult to read and interpret. This enhancement would allow SD-WAN tunnel connectivity to be consolidated and displayed as a single SD-WAN cloud object, similar to how other cloud-based network types are represented. Customers mapping SD-WAN environments would benefit from cleaner, more readable topology maps that better reflect the logical SD-WAN fabric rather than a dense mesh of point-to-point tunnel links.
NetBrain currently reloads the Script Manager window and resets it to its default state whenever a user switches away to another browser tab and then returns, causing the prior view or working state to be lost. This enhancement would allow Script Manager to retain its last active state so that returning to the tab restores the window as it was left. Preserving this state would reduce disruption to users working across multiple tabs and eliminate the need to manually re-navigate to their prior position within Script Manager.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.