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.
The Task Manager page in System Management currently only displays scheduled Discovery and Benchmark jobs, and this view cannot be sorted by last run time. Scheduled QApp, DVT/Parser, and Plugin jobs are not visible in this same interface, making it difficult for administrators to get a complete picture of all scheduled activity. This enhancement proposes expanding the Task Manager to list all scheduled job types, including QApp, DVT/Parser, Plugin, Benchmark, and Discovery, in a single consolidated table. The table should support sorting by last run time and allow administrators to pause individual jobs. This would give administrators a centralized way to review and manage scheduled workloads, which is particularly valuable when planning system upgrades or maintenance windows that require pausing scheduled activity in advance.
NetBrain's Change Management module currently integrates with Ansible worker servers but does not support direct integration with Ansible Tower. Customers whose Ansible Tower sits above their worker servers cannot call worker servers directly, and must rely on custom API-based workarounds to interact with Tower instead of using the Change Management module natively. This enhancement would add native Change Management support for Ansible Tower as an integration target, allowing jobs to be executed against Tower directly rather than through underlying worker servers. Direct Tower integration would remove the need for custom adapters, streamline playbook execution, and provide the execution and reporting data that customers use to demonstrate automation efficiency, cost savings, and time savings to leadership.
NetBrain's REST API currently does not provide a method to programmatically trigger full execution of a Change Management task, Runbook, Network Intent, or QApp. Existing API capabilities support limited data retrieval scenarios but do not extend to initiating a complete change or automation workflow. This enhancement would introduce REST API endpoints that allow external systems to trigger execution of Change Management tasks, Runbooks, Network Intents, and QApps directly, supporting both change-module-governed and standalone runbook execution paths. Customers integrating NetBrain with ticketing, orchestration, or monitoring platforms would gain the ability to fully automate network change processes, such as device upgrades, without requiring manual initiation through the NetBrain user interface.
Use case:We have scheduled weekly Auto discovery. So, the device count is changing over the time. At the same time I use ADT as a source for Golden Intent checks.Each time the number devices change or there is an update in ADT that is source for golden intent I need to Run & Publish either only for golden intent or for both golden feature and golden intent.I would like to have some automation to reflect in change of number of devices or ADT source table.I would like to ask to consider this feature.Created NetBrain Case #00177886
NetBrain currently does not support discovery and mapping of AWS Cloud WAN, a managed wide-area networking service used to interconnect cloud and on-premises networks. This enhancement would add native discovery, modeling, and topology mapping capabilities for AWS Cloud WAN resources, consistent with existing support for other AWS networking constructs. Customers migrating from AWS Transit Gateway to Cloud WAN would gain complete visibility into their evolving network architecture without relying on manual workarounds.
NetBrain currently recalculates L2 and L3 topology through a full nightly rebuild process, which can take several hours to complete across the entire network. Customers who make localized network changes, such as re-cabling a switch connection in a single office, must wait for the next full topology cycle before the updated connectivity is reflected in health checks and maps. This enhancement would introduce the ability to trigger an on-demand topology recalculation scoped to a selected site or map, rather than requiring a full network rebuild. Providing a targeted recalculation option would let customers validate recent physical or logical changes quickly, reducing wait time and improving the accuracy of near-real-time health monitoring.
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 currently requires users to manually run the 'analyze relevance' and 'generate assets' steps within the Golden Assessment Library each time a new device needs to be evaluated against golden assessment rules. This enhancement would introduce automated detection of newly discovered devices along with an automatic trigger of the relevance analysis and asset generation process, eliminating the need for manual intervention. Customers managing large or dynamic environments would benefit from consistent, up-to-date assessment coverage as new devices are added, reducing administrative overhead and the risk of gaps in compliance monitoring.
NetBrain's discovery and benchmark drivers for F5 BIG-IP devices have been validated primarily against the i-Series platform, and support status for the newer r-Series hardware, such as the BIG-IP r5600, is not clearly documented or confirmed. This enhancement would validate and formally support F5 BIG-IP r-Series devices as Discovery targets, including any driver adjustments needed to accommodate architectural differences from the i-Series line. Customers replacing end-of-support i-Series hardware with r-Series platforms would benefit from confirmed compatibility and continuity of Discovery and data retrieval without unexpected gaps.
NetBrain currently benchmarks device configuration using whichever method was used for discovery, so devices discovered via API do not have configuration data collected through CLI. This results in inconsistent configuration data formats across the device inventory, which limits the ability to process device configuration data through downstream systems that expect a standardized format, such as large language model based analysis. This enhancement would add an option to benchmark device configuration via CLI regardless of the discovery method used, ensuring all devices produce configuration data in a consistent format. Customers using AI-driven or automated analysis workflows would benefit from uniform, predictable configuration data across their entire device inventory.
NetBrain currently relies on a live NIST integration to retrieve and update CVE data, which cannot be used by deployments that have no internet access, even through a proxy. As a result, offline customers have no supported way to keep their CVE assessments current. This enhancement would provide a downloadable CVE data package that customers can manually transfer to an offline environment and upload into their NetBrain platform to refresh CVE assessments. This would allow customers operating in fully isolated networks to maintain up-to-date vulnerability assessments and meet ongoing security and compliance requirements without requiring direct internet connectivity.
NetBrain currently does not provide finalized, published documentation covering MCP Server setup, configuration, and usage for AI assistant integration, leaving customers without a clear reference for implementation. This enhancement would deliver comprehensive MCP documentation, including installation steps, configuration guidance, and usage instructions, as part of the standard online help and user guide materials. Customers integrating AI assistants through MCP would benefit from consistent, authoritative guidance that reduces onboarding time and reliance on direct support contact.
NetBrain does not currently provide a native or certified adapter for integrating with the EcoStruxure platform, which limits visibility into environments that rely on this system for infrastructure or facility management data. This enhancement would add a supported adapter for EcoStruxure within the Integrated Edition, enabling discovery and modeling of associated devices alongside other supported platforms. Customers operating EcoStruxure environments would gain consistent, supported integration and improved network visibility without relying on manual workarounds or custom-built solutions.
NetBrain's API Server Manager does not currently support Barracuda Control Center as an API source type, which prevents discovery of devices managed through that platform. This enhancement would add Barracuda Control Center as a selectable API source type, enabling discovery and modeling of associated devices alongside other supported platforms. Customers running Barracuda-managed infrastructure would gain complete device visibility without relying on manual workarounds.
Within Golden Config Discovery, the device groups used for applying configuration and features do not automatically update when new devices are added to the environment, requiring manual intervention to keep group membership current. Additionally, when new devices are incorporated, the process only applies configuration to them without performing verification, which leaves administrators without confirmation that the applied configuration is correct. This enhancement proposes that Golden Config Discovery automatically update its associated device groups as device inventory changes, and that newly added devices go through both an apply and a verify step as part of the same workflow. Customers managing dynamic environments would benefit from reduced manual maintenance and greater confidence that configuration changes are both applied and validated on new devices.
When a triggered automation API call includes a category data field, the system currently bypasses match condition evaluation and applies the provided category directly, rather than checking it against configured match conditions. This behavior prevents customers from restricting automated diagnosis triggers to only those issues that meet defined criteria when the integrated third-party system always supplies a category value. This enhancement proposes adding an option to enforce match condition evaluation even when an API-provided category is present, so the system can determine trigger eligibility based on configured conditions rather than defaulting to the supplied value. Supporting this option would give customers finer control over which incoming events trigger diagnoses, reducing unnecessary automation runs from integrations that always populate the category field.
The CVE dashboard currently displays vulnerability alerts without a means to group or filter them by CVSS Base Score. This enhancement would add a filter or grouping option based on standard CVSS severity bands, allowing users to select one or more bands and view a summarized count of alerts per tier. Customers responsible for vulnerability remediation would gain the ability to quickly prioritize Critical and High severity alerts rather than manually reviewing the full alert list.
NetBrain does not currently include a driver for Actelis ML638 VDSL Modem devices, which prevents discovery and benchmarking of this device type. This enhancement would add a discovery and benchmark driver for the Actelis ML638, enabling NetBrain to collect device configuration and topology data consistent with other supported device types. Customers operating Actelis ML638 modems within their network would benefit from complete topology visibility and reduced manual mapping effort.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.