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 built-in SCP client for uploading and downloading device configuration files or performing firmware upgrades, nor does it offer a scriptable SSH client for automated device interaction. This limits the platform's ability to manage devices that rely on SCP and scripted SSH workflows, such as networked UPS systems, within a single tool. This enhancement would add native SCP client functionality alongside a scriptable SSH client, enabling automated configuration backup, restore, and firmware upgrade tasks directly from NetBrain. Customers managing large fleets of third-party network-connected devices would benefit from consolidating auditing and configuration management into NetBrain, reducing reliance on custom external scripts and improving operational consistency.
NetBrain currently displays device field data on maps in a fixed, static position, giving users no ability to reposition this text for improved layout. This enhancement would allow users to move device field labels freely within the map canvas to accommodate custom arrangements. Customers building large or densely populated maps would benefit from improved readability and layout flexibility without being constrained by fixed label placement.
Site Manager currently requires users to manually click the expand arrow on each individual site to view its contents, with no option to open or close all sites at once. This enhancement would add an Expand All and Collapse All shortcut control to the Site Manager interface, allowing all sites in the list to be expanded or collapsed with a single click. Customers managing a large number of sites would benefit from faster navigation and reduced repetitive manual clicking when reviewing the site hierarchy.
NetBrain currently does not provide a consolidated dashboard view that displays all tasks that are actively running, particularly Automation Tasks, at a given point in time. Users must check individual task lists or logs separately to determine what is currently in progress across the system. This enhancement would add a dashboard widget or view that aggregates and displays live, in-progress tasks, with particular visibility into running Automation Tasks. Customers managing large-scale or concurrent automation activity would gain a single point of reference to monitor active work, helping them identify long-running or stalled tasks and better plan operational activity without navigating multiple screens.
The Triggered Automation dashboard currently limits users to a fixed set of predefined time range filters and does not offer a 'Last 1 Month' preset or the ability to define a custom date range when reviewing task activity. This enhancement would add a custom time range selector along with a 'Last 1 Month' option to the dashboard's filtering controls. Customers managing longer-running automation activity would gain more flexibility to review and analyze task history over the periods most relevant to their operational and reporting needs.
NetBrain currently does not indicate, within Benchmark logs, whether a retrieved table such as a routing table was collected via CLI or SNMP. This makes it difficult to determine the data source during troubleshooting, and the only available workaround is to disable the SNMP routing feature in the driver to force CLI-based retrieval. This enhancement would add a clear indicator or filter within Benchmark logs to distinguish CLI-retrieved tables from SNMP-retrieved ones. Customers troubleshooting data discrepancies would benefit from faster identification of the retrieval method without modifying driver configurations.
NetBrain's Front Server registration process currently does not honor proxy settings configured at the system or browser level, which prevents Front Servers from completing registration with the Front Server Controller in environments where outbound connectivity requires a proxy. This enhancement would update the Front Server registration workflow to detect and route through configured proxy settings when establishing its connection to the Front Server Controller. Customers deploying Front Servers in proxy-restricted or cloud network environments would benefit from a successful, unattended registration process without requiring manual network reconfiguration or workarounds.
NetBrain currently generates a separate CSV file for each Network Intent within an Automated Data Table, requiring users to manually open and cross-reference multiple files when reviewing results across different checks. This enhancement would allow the outputs of multiple intents within an ADT to be merged into a single consolidated CSV file. Customers performing configuration drift analysis across multiple features, such as NTP, AAA, banners, and ACLs, would benefit from a unified view of all findings without manual file consolidation.
NetBrain currently supports ServiceNow change management triggered automation using legacy Gapp and QApp constructs, which operate separately from the Network Intent framework and cannot take advantage of Intent-based capabilities such as diagnosis, reporting, and standardized workflow logic. This enhancement would provide a path to convert or migrate existing Gapp and QApp based automation, triggered by ServiceNow change management events, into equivalent Network Intent workflows. Customers relying on ServiceNow-driven automation would benefit from a consistent, Intent-based automation model that improves maintainability and aligns legacy workflows with current platform capabilities.
NetBrain currently does not support automatically sending an email alert and non-compliance report when a Network Intent template detects a configuration discrepancy, such as a mismatch between startup and running configuration. Users must manually review comparison results within the platform to identify non-compliant devices. This enhancement would allow a Network Intent template to trigger an automated email notification, including a non-compliance report, whenever the defined comparison logic identifies a discrepancy. Customers responsible for configuration compliance would benefit from immediate, proactive visibility into non-compliant devices without needing to manually monitor comparison results.
NetBrain currently has no mechanism to suspend live access to specific devices during planned maintenance windows, which can result in failed access attempts, false alerts, or interference with ongoing maintenance work. This enhancement would allow administrators to place one or more devices into a Maintenance Mode with a configurable start and end datetime. While a device is within its maintenance window, NetBrain would skip all live access to that device, including scheduled discovery, on-demand CLI, path diagnosis, and runbook execution, then automatically resume normal access once the window expires. Customers performing scheduled device maintenance would benefit from reduced false alerts and fewer disruptions to maintenance activities, along with the convenience of automatic access resumption without manual intervention.
NetBrain path calculation today supports IP-based, TCP-based, and multicast path types, but does not offer a native path type where the source is a device and the destination is a VLAN for Layer 2 tracing. Customers can approximate this only through a plugin-based workflow that requires manually specifying source device, VLAN, interface, and destination device interface and VLAN, rather than a streamlined native calculation. This enhancement would add a native path type, positioned alongside existing IP and multicast path options, that accepts a source device and destination VLAN and calculates the traversed Layer 2 path across transport technologies such as VPWS, EVPN, Q-in-Q, and standard trunking. Customers operating complex Layer 2 transport environments would gain built-in, consistent path visibility for VLAN-based traffic without relying on plugin workarounds, reducing manual effort during troubleshooting.
NetBrain currently supports integration with the classic Aruba Central platform, but does not support the newer Aruba Central platform, which uses a different authentication method and returns API output in a different structure. This enhancement would add a dedicated integration path for the new Aruba Central platform, including its updated authentication flow and API response handling, so that discovery and monitoring can function correctly against it. Customers who have migrated or are migrating to the new Aruba Central platform would gain continued visibility and management capability without being blocked by the underlying platform change.
The Audit Log for Device Access currently records that a device access occurred and when, but does not capture the execution context behind the event. Users have no way to determine which task, process, or worker server initiated a given access without manually cross-referencing multiple server logs. This enhancement would add three fields to each Audit Log for Device Access entry: the triggering task name or type, the associated process ID, and the worker server that executed the task. Providing this execution context would allow administrators and support teams to trace the origin of any device access event directly from the audit log, reducing the time and effort required for troubleshooting.
NetBrain's AI assistant does not currently suggest example prompts or organize them by topic to help users understand what questions they can ask when starting a session. This enhancement would introduce AI-suggested prompts grouped by topic, such as Assets, Cases, and Troubleshooting, presented to users at the start of an AI interaction. Providing these guided starting points would help new users become productive more quickly by clarifying the types of questions the AI feature can answer.
NetBrain DVT can display an inconsistent view of retrieved IPv4 address data for MSEE links: the address renders correctly on some existing maps but fails to appear on newly created maps for the same device, even though the address is confirmed present in the underlying DVT log. This enhancement would ensure that DVT consistently renders retrieved IPv4 address data for MSEE links regardless of which map instance is used. Consistent display of validated data would help customers trust DVT results and avoid unnecessary troubleshooting caused by display discrepancies.
NetBrain's ServiceNow connector health check currently returns a generic 'Connector is not healthy' timeout message when a connection attempt fails, without providing detail on where the failure occurred, such as the mid server, load balancer, or the NetBrain API service itself. This enhancement would add detailed diagnostic logging and a clearer error breakdown to the connector health check process, allowing administrators to pinpoint the specific point of failure. Customers troubleshooting intermittent or environment-specific connectivity issues between ServiceNow and NetBrain would benefit from reduced diagnostic effort and faster issue resolution.
NetBrain currently does not provide a way to export Runbook templates, along with their dependent backend components such as intents and ADT tables, from the Build and Download Library section of the Automation Center. This enhancement proposes adding a native export capability that packages a Runbook template together with its associated automation assets into a single downloadable file. This would allow customers to back up, migrate, or share complete Runbook configurations across environments without manually recreating dependent components, reducing setup effort and the risk of missing dependencies.
NetBrain currently does not support a fully automated end-to-end change management workflow with ServiceNow. Change Requests must be manually triggered, planned dates are not automatically selected based on defined scheduling logic, and reschedule events are not automatically detected or handled. This enhancement would allow NetBrain to automatically trigger Change Request creation in ServiceNow, apply configurable logic to determine the planned implementation date, and detect and respond to reschedule events so that both systems remain synchronized throughout the change lifecycle. Customers would benefit from a consistent, hands-off change management process that reduces manual coordination and scheduling errors between NetBrain and ServiceNow.
Geolocation dashboard maps currently can continue to display devices that have already been removed from the domain, even when those devices no longer appear in Data Accuracy Resolution or other inventory views. This creates a discrepancy between the actual device inventory and what is rendered on the geolocation map. This enhancement would have the geolocation dashboard reconcile its device list against current domain inventory each time it refreshes, automatically excluding devices that have been decommissioned or removed. Customers would benefit from accurate, trustworthy dashboard visualizations that reflect the true state of their network without manual intervention to clear stale entries.
When defining a shared automation library, certain configuration options are currently placed under an advanced section that is collapsed or hidden by default, making them easy to overlook during setup. This enhancement would display these advanced options by default within the share automation library definition screen, rather than requiring users to expand a hidden section. Surfacing these options up front would help administrators configure shared libraries correctly and reduce the risk of missing settings considered important to the library definition.
NetBrain currently adds new credential entries to the bottom of the credentials table in Domain Management Network Settings, with no efficient way to reposition an entry within the list. Administrators who need to move a newly added credential higher in the list must go through a lengthy manual process. This enhancement would introduce a streamlined way to resequence credential entries, such as drag-and-drop reordering or a move-up/move-down control. Customers managing large credential lists would benefit from reduced administrative effort and faster organization of credential priority order.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.