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's Preventive Automation Manager currently does not display sufficient detail about what occurs after a Network Intent is submitted for execution, leaving users unable to track its progress or outcome from that view. This enhancement would add configurable columns or fields to the Preventive Automation Manager grid to surface execution status and related details for each submitted intent. Customers running preventive automation at scale would benefit from improved visibility into execution activity without needing to navigate to separate logs or screens.
NetBrain currently does not provide a way to compare paths calculated within Application Manager against actual traceroute results, making it difficult to pinpoint hops where the path calculation engine resolved an incorrect next hop. This enhancement would add a comparison capability that runs a traceroute alongside the application's calculated path and highlights any discrepancies in next-hop resolution between the two. Customers would gain a faster, more reliable way to validate application path accuracy and troubleshoot cases where automated path calculation diverges from actual traffic flow, reducing manual verification effort.
NetBrain currently displays only one of the two CheckPoint Multi-Domain Server environment views at a time, since the platform surfaces results from either the data plane or management plane command output but not both concurrently. This enhancement would allow NetBrain to capture and display output from both environment commands so that data plane and management plane information are both accessible within the device view. Customers managing CheckPoint Multi-Domain Server deployments would gain complete visibility into both operational planes without needing to manually switch between commands or lose access to one data set.
NetBrain currently requires users to manually build and link individual site maps into a consolidated view when they need a single map representing all sites at a location; there is no automated way to assemble a full multi-site topology in one step. This enhancement would introduce an automated capability to generate a combined map covering all sites at a given location, incorporating live health status and link monitoring for the devices within that map. Customers managing many distributed sites would gain a faster, less error-prone way to obtain a unified, continuously monitored view of their network without manually building and maintaining each site connection.
NetBrain currently does not provide a consolidated, platform-wide health check that validates the integrity of underlying data across all modules and element tables. Administrators today must rely on manual investigation to identify issues such as invalid records, which can take a significant amount of time to isolate and resolve. This enhancement would introduce an automated, one-shot sanity check utility that scans the platform's modules and element tables to detect data integrity issues and surfaces the results to administrators. Providing this capability would give customers proactive visibility into overall platform health beyond existing domain management checks, reducing the time and effort required to identify and address underlying data issues.
NetBrain inventory does not currently include a criticality attribute that can be assigned to and displayed for each asset. This enhancement would add a criticality field available across all assets in the inventory, allowing values to be set and viewed consistently within inventory reports. Customers would benefit from the ability to classify assets by importance, supporting prioritization in monitoring, troubleshooting, and change management workflows.
NetBrain path and map visualization currently does not display the Layer 2 segment of a Cisco ACI fabric when the calculated path traverses an HSRP gateway, resulting in an incomplete topology view for these environments. This enhancement would extend map rendering and path calculation logic to correctly detect and display ACI fabric Layer 2 connectivity when HSRP is used as the gateway protocol. Customers operating ACI fabrics with HSRP-based gateways would gain complete end-to-end topology visibility, reducing the need for manual verification during troubleshooting.
NetBrain does not currently provide a native tool for managing the underlying NoSQL database used by the platform, requiring administrators to rely on external database utilities or command-line access for maintenance tasks. This enhancement would introduce a database management tool integrated directly within the base NetBrain software, allowing administrators to perform routine NoSQL database operations from within the product interface. Customers would benefit from a more streamlined administrative workflow and reduced dependency on separate third-party database tools.
NetBrain currently enforces a fixed attachment size limit for scheduled QApp email delivery, and there is no configurable option to adjust this threshold. When a generated CSV report exceeds the limit, the file is not sent, and the only workarounds are exporting to a shared network folder or manually exporting the file. This enhancement proposes allowing the attachment size limit for scheduled QApp email output to be configured, so that larger CSV reports can be delivered automatically. Customers who rely on scheduled reporting for larger datasets would benefit from uninterrupted automated delivery without needing manual intervention.
NetBrain currently does not provide a visual indicator on individual runbook nodes to show whether a node has completed execution or what status result it produced during a Change Management run. This enhancement would add a highlight or border to each node once it has been executed, reflecting its completion state and outcome directly on the runbook canvas. Customers running multi-step change runbooks would benefit from improved at-a-glance visibility into execution progress and results, reducing the need to inspect each node individually to track change status.
Network Change runbooks currently require each node, such as Benchmark Before, Execute, Benchmark After, and Compare, to be added individually when building a multi-step change. This becomes repetitive when a runbook needs to represent multiple discrete changes in sequence. This enhancement would allow users to insert a predefined cluster of related node types as a single action, rather than adding each node one at a time. Customers building runbooks with multiple change segments would benefit from faster runbook construction and more consistent structure across change steps.
NetBrain currently does not provide a way to consolidate table data collected from multiple devices, such as MAC address tables, into a single spreadsheet that identifies the source device for each row. Users must manually combine separate per-device outputs and add the hostname themselves before the data is usable for analysis. This enhancement proposes adding a capability to select multiple devices from a site map, collect a specified data table across those devices, and export the combined results into a single Excel sheet with the device hostname included as a column alongside the existing table fields. Customers managing multiple switches would benefit from reduced manual effort when compiling cross-device table data for network analysis and reporting.
NetBrain currently does not provide a way to schedule automatic export of the OneIP Table to CSV format with delivery to an external server via FTP. Users who need recurring IP data extracts must run the export manually each time and transfer the file separately. This enhancement proposes adding a scheduling option for OneIP Table export that generates a CSV file on a defined recurring basis and automatically transfers it to a specified FTP destination. Customers who rely on recurring IP inventory data for downstream systems or reporting would benefit from reduced manual effort and more consistent, timely data delivery.
The Overall Health Check Runbook template does not currently include a column or row displaying interface traffic capacity, limiting visibility into bandwidth-related metrics during a health check review. This enhancement would add an interface capacity field to the template so capacity data is presented alongside existing interface health metrics. Customers performing network health assessments would benefit from having capacity information readily available without needing to reference a separate report.
NetBrain does not always correctly calculate Layer 3 links between devices that share a common subnet, even when each device has a properly discovered interface and IP address. In some cases no link is drawn between devices in the same subnet despite other L3 links existing for that subnet, and in other cases a link is drawn but fails to attach to the existing link group for that subnet. This enhancement would improve the L3 link calculation logic to reliably identify and connect all devices sharing a common subnet into a single, accurate link representation on the topology map. Customers relying on automated L3 topology mapping would gain more complete and trustworthy network diagrams, reducing the need for manual link correction and improving confidence in troubleshooting and documentation.
NetBrain currently generates only a single page, limited to L3 topology, when a map is created through an event template or QApp workflow, unlike standard site maps that provide separate L3, L2, and Neighbor pages. This enhancement would extend event-template and QApp-based map generation to include additional pages for L2 topology and Site Neighbor views, matching the page structure already available in standard site maps. Customers relying on automated map generation would gain consistent, multi-layer topology visibility without needing to manually build supplementary maps to view L2 or neighbor relationships.
NetBrain's ServiceNow V2 automation trigger configuration currently does not support filtering incoming incidents based on Configuration Item (CI) fields, limiting customers to broader trigger conditions when defining which incidents initiate automation. This enhancement would allow trigger rules to include filter conditions based on CI attributes, so automation only executes for incidents tied to matching configuration items. Customers with diverse device and asset inventories would benefit from more precise trigger scoping, reducing unnecessary automation runs and improving relevance of triggered diagnostics.
NetBrain's discovery and benchmark drivers for certain platforms, including Cisco Nexus, ASR, and IOS Switch, can treat expected informational responses, such as messages indicating a feature like CDP is not enabled, as invalid or failed command output rather than a valid result. This enhancement would update the affected drivers to recognize these known response patterns as valid, non-error output, allowing discovery and benchmark tasks to complete without unnecessary failures. Customers operating devices where certain features are intentionally disabled would benefit from more accurate task results and fewer false error indications during discovery and benchmarking.
NetBrain currently allows users to locate map-sharing recipients only by username, which is limiting for organizations using an external authentication source, such as AD, where the username field may be populated with a non-descriptive identifier rather than a recognizable name. This enhancement would allow administrators to configure which user attribute, such as display name or email address, is used for recipient search when sharing maps. Customers relying on external authentication systems would benefit from a more intuitive and efficient recipient lookup experience when sharing maps via email.
NetBrain currently does not provide a way to save advanced search filter configurations for later reuse in the primary search bar. This enhancement would allow users to name and save a set of advanced search criteria, then select it from a saved list on subsequent searches. Customers who frequently build complex, multi-option searches would save time and reduce repetitive setup by reapplying previously saved filter configurations.
The Preventive Automation Manager currently displays a device count under Monitoring Probe even when none of those devices actually have a monitoring probe enabled, which creates confusion about the true probe status. This enhancement would revise the wording or labeling of this field to clearly distinguish between devices eligible for monitoring probes and devices with probes actively enabled. Clearer labeling would reduce misinterpretation and support more accurate decision-making for customers managing preventive automation configurations.
When a Front Server Group is used to retrieve data from a device, the system does not currently track or reuse an existing authenticated session on a specific Front Server. As a result, subsequent data retrieval tasks for the same device can be randomly assigned to a different Front Server within the group, even when another Front Server already holds an active session with that device. This enhancement would introduce session-aware task assignment within Front Server Groups, so that when an active session exists on a Front Server for a given device, subsequent retrieval tasks for that same device are routed to the same Front Server rather than establishing a new session elsewhere. Customers operating Front Server Groups would benefit from a reduction in redundant authentication events and associated login logs, improving efficiency and reducing unnecessary load on monitored devices.
Dynamic Device Group search currently does not support filtering for devices where a given attribute field is NULL or empty. As a result, administrators cannot easily isolate devices with missing configuration data, undefined device types, or other incomplete attribute values using search alone. This enhancement would add NULL or empty value matching as a selectable condition within the Dynamic Device Group search interface. Customers would be able to quickly identify and group devices with missing or incomplete data for further investigation, improving data accuracy and reducing the manual effort required to find these devices individually.
NetBrain's REST API currently does not provide a way to retrieve the execution status of tasks generated through Runbook-Based Triggered Automation, nor a way to determine whether a resulting map contains any devices. Customers running large-scale automated mapping cannot programmatically identify failed tasks or empty maps and must instead review each task manually through the user interface. This enhancement would introduce REST API endpoints that return the status (such as Finished or Failed) of Runbook-Based Triggered Automation tasks, along with an endpoint or field indicating the device count on a given map. Customers automating large volumes of path creation would gain the ability to identify incomplete or empty results at scale and trigger corrective actions without manual review, improving reliability and efficiency of automated mapping workflows.
Network Intent Template device qualification currently does not recognize MPLS Cloud as a selectable device type, preventing templates from being scoped or filtered to include MPLS Cloud objects. This enhancement would add MPLS Cloud to the list of device types available for qualification criteria within Network Intent Templates. Customers building intents that need to account for MPLS Cloud topology would benefit from more complete and accurate device targeting without 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.