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 display IPv6 neighbor information for a device when viewed from within a Site topology map, limiting visibility into IPv6-based connections at the site level. This enhancement would extend the Site map neighbor display so that IPv6 neighbor relationships are shown from the device end, consistent with existing neighbor visibility for other address types. Customers operating IPv6-enabled or dual-stack environments would gain more complete topology visibility within Site maps without needing manual cross-referencing to confirm IPv6 neighbor connections.
The Device Health Report currently reports a count of L2 topology issues per device but does not identify which specific interface is associated with each flagged issue. When a device has multiple interfaces, customers cannot determine which one requires attention without manual investigation. This enhancement would add interface-level detail to topology issue entries in the Device Health Report, so each flagged issue clearly references the affected interface name. Customers managing a large number of topology issues would be able to prioritize and resolve them more efficiently, reducing the manual effort needed to isolate the root cause among multiple interfaces on a device.
NetBrain's REST API currently does not provide a documented endpoint for retrieving Fine Tune statistics for a domain, including device counts and identifying details for fully CLI-accessed devices, SNMP-only devices, missed devices, devices with unknown SNMP SysObjectID, unknown IP addresses, and subnets with conflicted IPs. This limits customers who want to build automated reporting or monitoring workflows around Fine Tune results without relying on manual review through the user interface. This enhancement would introduce a REST API endpoint that exposes Fine Tune statistics for a specified domain, returning the counts and associated hostname or IP details for each of the categories above. Customers integrating NetBrain with external automation or reporting systems would benefit from consistent, programmatic access to Fine Tune data, enabling further automation and reducing reliance on manual lookup.
NetBrain currently supports configuring a single jumpbox hop when establishing Smart CLI connections to end devices, with no mechanism to define a sequence of two or more jumpboxes in a chain. This enhancement would allow administrators to configure multiple jumpboxes in a chained sequence, so that a Smart CLI session can traverse each hop in order to reach the target device. Customers operating segmented or layered network environments that require multiple jump hosts to reach end devices would gain full connectivity through Smart CLI without relying on manual, unsupported workarounds.
NetBrain currently allows Event templates for third-party integrations to be configured only at the domain level, requiring administrators to manually recreate or copy the same template into every domain. This enhancement would allow Event templates to be defined and managed at the Tenant and System level, so they can be applied across multiple domains without duplication. Customers managing large multi-domain environments would benefit from reduced administrative effort and more consistent event configuration across their organization.
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 does not currently publish verified or recommended local LLM models, inference engines, or hardware specifications for customers who want to run local LLMs instead of the default OpenAI-based models. This enhancement would provide documented guidance identifying certified local LLM models, verified inference engines, and recommended server specifications needed to support these models at expected performance levels. Customers who require on-premises LLM deployment for data security, compliance, or connectivity reasons would gain clear implementation guidance and confidence that their local environment meets NetBrain's operational requirements.
NetBrain currently requires administrators to manually enter Telnet/SSH login credentials one at a time in Network Settings, which becomes time-consuming in environments where each network device is assigned a unique set of credentials. This enhancement would add a bulk import capability, such as a CSV-based import process, allowing administrators to register multiple sets of login credentials into Network Settings in a single operation. Customers managing large device inventories with unique per-device credentials would benefit from significantly reduced manual setup effort and faster onboarding of new environments.
NetBrain currently applies its concurrent task execution limit, configured under System Management Task Manager, only to Discovery and Benchmark tasks that are scheduled to run. Tasks initiated through Run Now are not counted against this limit, so the total number of simultaneous task executions can exceed the configured maximum when manual runs occur alongside scheduled ones. This enhancement would extend the existing concurrency limit setting to also include Run Now-initiated Discovery and Benchmark tasks, so that the combined count of scheduled and manually triggered executions is constrained by a single configured maximum. This would help administrators, particularly in multi-tenant or multi-domain environments, avoid overloading the NetBrain system and network devices due to unplanned concurrent task execution.
NetBrain's live access log currently displays timestamps without consistent timezone labeling, and different features within the log may show local time, UTC, or another reference zone without indicating which is used. This creates ambiguity when interpreting log entries, particularly during troubleshooting across distributed teams or time zones. This enhancement would add explicit timezone labels to all timestamps shown in the live access log, ensuring consistency across the features that populate it. Customers and support teams would benefit from reduced confusion and faster, more accurate troubleshooting when reviewing live access history.
NetBrain currently does not support automatically initiating a Deep Diagnosis run when a scheduled Network Intent detects an alert; users must manually review Network Intent results and separately launch Deep Diagnosis to investigate root cause. This enhancement would allow a scheduled Network Intent to automatically trigger a Deep Diagnosis session upon detecting an anomaly, creating a closed-loop workflow from scheduled health check to automated root-cause analysis without manual intervention. Customers relying on scheduled monitoring would benefit from faster incident response and reduced manual effort in correlating alerts with diagnostic investigation.
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.
Deep Diagnosis currently troubleshoots only against live, real-time data and has no mechanism to reference its own history of previously executed queries and results when a user asks about an issue that occurred at a past date and time. This enhancement proposes enabling Deep Diagnosis to search prior executed queries and results, including both scheduled (TAF) and user-triggered runs, to identify the closest historical match to a predated issue and surface the associated findings or resolution. Customers investigating issues that are no longer live would benefit from faster root-cause identification without needing external historical data sources.
NetBrain currently exposes a configuration field intended solely for internal use within the administrator interface, with no option to hide it from standard view. Because this field is visible, users may unintentionally modify it, leading to operational issues even after being advised against changing it. This enhancement would introduce the ability for administrators to hide internal-use-only configuration fields from the GUI, ensuring they remain accessible only through supported internal channels. Limiting visibility of sensitive or internal configuration values would reduce the risk of accidental misconfiguration and decrease the volume of related support inquiries.
GAL dashboards currently default to displaying results from only the last 7 days. When a dashboard is opened for the first time more than 7 days after intents were executed, it appears blank even though valid results exist, requiring users to manually adjust the time range or re-run intents to see data. This enhancement would extend the default visibility window, such as to 30 days, or change the default behavior to show the most recently executed results regardless of when they ran. This would present a more complete and accurate view of dashboard data on first access, improving the onboarding experience and reducing the perception of missing or broken results.
AI Settings for the Deep Diagnosis Agent currently require device groups to be added statically, meaning membership does not update automatically when the underlying Shared Groups change. This enhancement would allow the Deep Diagnosis Agent's device group configuration to sync on a scheduled basis, such as daily or weekly, reflecting changes made to the source Shared Groups. Customers managing dynamic environments would benefit from reduced manual maintenance and more accurate diagnosis coverage without needing to manually re-add or update device groups.
The Audit Log Search page currently loads data automatically before a user defines a time range or module, resulting in long initial load times, and it does not retain previously used search criteria when the page or tab is reopened, requiring the user to redefine search parameters each time. This enhancement would require users to manually select the desired time range and module and click Search before the query executes, rather than triggering an automatic load, and would additionally retain the most recent search criteria across sessions. Administrators reviewing audit logs would benefit from reduced wait times and fewer repeated steps when performing routine log searches.
NetBrain's OAuth implementation currently requires each client integration to be manually registered and configured by an administrator before it can authenticate, with no support for clients to register themselves programmatically. This limits organizations that connect multiple dynamic or third-party MCP clients, as each new client requires manual setup effort before it can establish a connection. This enhancement would add support for OAuth Dynamic Client Registration, allowing compatible clients to register with NetBrain's authorization server automatically and receive credentials without administrator intervention for each individual client. Customers integrating a growing number of AI assistant or automation tools would benefit from reduced administrative overhead and faster, more consistent onboarding of new OAuth-based integrations.
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 offer a native or certified integration with AppDynamics (AppD), a widely used application performance monitoring platform. This enhancement would add a supported integration that allows NetBrain to exchange device and monitoring data with AppD, enabling cross-referencing of network visibility data with application performance insights in a manner consistent with existing APM integrations. Customers evaluating or running AppD alongside NetBrain would benefit from consolidated visibility across network and application layers, reducing manual effort in correlating data between the two platforms.
NetBrain's Golden Assessment Library currently does not include validated assessment content for Opengear devices, leaving these devices without out-of-the-box configuration compliance checks. This enhancement would extend the Golden Assessment Library to natively support Opengear devices, enabling standard assessment and compliance checks through Deep Diagnosis and Runbook Companion workflows. Customers operating Opengear devices would benefit from consistent, supported assessment coverage without needing to build and maintain custom checks.
The Runbook Document node currently allows users to include information only from specific action nodes, such as Map, CLI, Device, Intent, Config Check, Change, and QApp, but does not support pulling in AI Companion results. This enhancement would add AI Companion output as an available content source within the Document node, allowing its results to be incorporated directly into generated runbook documentation. Customers would benefit from more complete documentation that combines AI-driven analysis with existing runbook execution details, improving reporting and review workflows.
NetBrain's Golden Assessment Library currently does not include validated assessment content for A10 or ATEN Load Balancer devices, leaving these platforms without coverage in Deep Diagnosis and Runbook Companion workflows. This enhancement would extend Golden Assessment Library support to include A10 and ATEN Load Balancer drivers, enabling standard configuration compliance checks for these platforms. Customers operating A10 or ATEN Load Balancers would benefit from consistent, supported assessment coverage without needing to build and maintain custom checks.
NetBrain's MCP server currently returns network-related data to all authenticated users without regard to their assigned role, meaning any user with access to the AI assistant can receive the same level of detail regardless of their intended scope of visibility. This enhancement would introduce role-based access control for MCP server responses, allowing administrators to define which categories of network data a given role is permitted to receive through AI-driven queries. Organizations with segmented teams, such as application owners who should not see sensitive network infrastructure details, would benefit from tighter data governance and reduced risk of unintended information exposure through the AI assistant.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.