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 export the devices shown on a map into a structured inventory host file suitable for automation platforms such as Ansible. Users must manually compile device lists and connection order, which is time-consuming and error-prone for large or interconnected networks. This enhancement proposes an export capability that generates an inventory host file directly from a map, reflecting the topology and connection order of devices, with the ability to exclude specific devices or device types from the output. Customers managing large-scale automation workflows would benefit from reduced manual effort and more accurate, up-to-date inventory files that align with their network topology and change management sequencing needs.
NetBrain currently does not provide a consolidated way to export system-level details such as Tenants, Domains, Sites, Device access status categories, Scheduled tasks, and license information into a single spreadsheet. This enhancement proposes adding a system-level export capability that allows administrators to generate a CSV or Excel report containing this combined information. Customers managing large multi-tenant environments would benefit from a streamlined way to compile system-wide data for reporting and auditing purposes without manually gathering information from multiple screens.
NetBrain path trace currently calculates paths correctly from an internal device toward an Internet Cloud or MPLS L3 Cloud object, but does not reliably calculate the reverse path, from the cloud object back to the internal destination address. This enhancement would extend the path calculation engine to support accurate bidirectional tracing through Internet Cloud and MPLS L3 Cloud objects, so that paths originating from these cloud representations resolve correctly to the intended internal destination. Customers who rely on path trace to troubleshoot inbound traffic flows would gain complete, accurate visibility in both directions without needing manual workarounds.
NetBrain's compare feature currently produces output that is rich-text formatted, which requires manual cleanup when pasted into plain-text aware tools such as Notepad or terminal applications. Additionally, the compare export is limited to a zipped HTML file, with no option to export results in a unified diff format. This enhancement proposes providing a copy-paste ready, plain-text version of the compare window output, along with an additional export option that generates results in unified diff format alongside the existing HTML export. This would allow customers to more easily incorporate compare results into plain-text workflows, documentation, and version control systems without manual reformatting.
The API service currently restricts the number of times a Qapp or DVT can be triggered to retrieve live data, capping execution at approximately 100 runs per session. This limit prevents extended automated monitoring scenarios that require frequent, repeated data collection over a longer duration. This enhancement would raise the maximum execution count for API-triggered live data retrieval, allowing sustained polling intervals across extended time periods. Customers running continuous automation workflows would gain the ability to schedule frequent live data checks without hitting an artificial execution ceiling, supporting long-running monitoring and diagnostic use cases.
NetBrain's QApp debug mode currently provides only log output when a custom Python script fails, making it difficult to identify which portion of the script caused the error. Customers often must repeatedly run the QApp against a map to manually isolate the failing logic, which slows down the troubleshooting process. This enhancement proposes adding more granular debugging capabilities to QApp, such as script-level breakpoints, step-by-step execution tracing, or clearer error localization within logs. It also proposes a built-in, criteria-based table creation option to reduce reliance on custom Python scripting for common table-building tasks. These improvements would reduce troubleshooting time and streamline table operations for customers building advanced automation workflows.
Change Control workflows today require separate 'Define Change' and 'Execute Change' tasks even when a customer uses an Ansible runbook, which already fulfills the requirements of both steps. As a result, the Ansible task is treated as a secondary validation step rather than as the core change itself. This enhancement would introduce a Change Control flow optimized for Ansible-based changes, where a single Ansible runbook task satisfies both the definition and execution requirements. Once the change is approved, the Ansible task would be locked in the same manner that the 'Define Change' task is locked today. This would simplify the change process for Ansible-oriented teams, reduce redundant steps, and align the platform's change workflow with existing automation practices.
NetBrain does not currently provide an adapter for onboarding Cisco Telemetry Broker (CTB) devices via API, which limits visibility into environments that rely on this platform for telemetry management. This enhancement proposes adding a dedicated CTB adapter, along with documentation of the vendor API details required for integration. Supporting CTB would allow customers to fully onboard and manage these devices within NetBrain, extending discovery and monitoring coverage to telemetry broker infrastructure.
NetBrain currently requires each user to manually select the 'Execute Changes in Bulk' option each time a change template is created, with no way to set this behavior as a default across the organization. This enhancement would introduce an administrator-configurable global setting that allows the 'Execute Changes in Bulk' option, and potentially other change-execution behaviors, to be set as the default for all users. Administrators would define the setting once, rather than relying on each user to configure it individually. This reduces repetitive manual configuration, ensures consistent change-execution behavior across teams, and lowers the risk of inconsistent settings when multiple users create templates independently.
NetBrain does not currently provide a validated or natively supported adapter for integrating with Arista DANZ monitoring fabric devices, requiring customers to build and maintain their own custom adapters. This enhancement would add native support for Arista DANZ within the Integrated Edition, including a certified adapter that can be verified and maintained by the product team. Customers operating Arista DANZ environments would benefit from consistent, supported integration rather than relying on unverified custom-built adapters, reducing maintenance overhead and improving reliability of network visibility data.
Golden Configuration parsing currently treats JSON-formatted content as plain text, so start and end line markers break the JSON structure and prevent it from being recognized as valid JSON. As a result, parent and dependency options available for other configuration patterns cannot be applied to JSON blocks, and complex scenarios involving multiple JSON fragments or variables produce a flattened table instead of a single reconstructed JSON object, forcing instance-based checks where a single key/value check would suffice. This enhancement would extend the parsing engine to recognize and preserve JSON formatting, allowing parent and dependency options to apply to JSON patterns, and would add the ability to reconstruct or reassemble parsed JSON fragments into a single cohesive structure when building the golden configuration. Supporting native JSON parsing would let customers isolate and validate specific configuration segments, such as edge-specific portions separate from profile-level configuration, while relying on straightforward key/value based checks rather than complex instance-based workarounds.
NetBrain currently defaults the login screen to the local NetBrain authentication method, requiring users to manually switch to SSO each time they log in, even in environments where every user authenticates exclusively through SSO. This enhancement would allow administrators to configure SSO as the default authentication method presented on the login screen. Customers operating in SSO-only environments would benefit from a streamlined login experience, reducing unnecessary manual steps for every user session.
NetBrain currently does not provide a way to duplicate a map under a new name while preserving the runbook's per-device command associations. When a map is saved as a new map, the runbook and its results are lost, and when a runbook is saved as a template, the per-device command scoping is not preserved, causing all commands to be applied to every device instead of only the intended ones. This enhancement would allow a map to be duplicated or renamed with its runbook intact, retaining the specific command-to-device associations exactly as configured in the original map. Customers who repeatedly execute similar changes across the same set of devices would save considerable time by reusing a proven runbook configuration instead of manually re-entering device-specific commands for each new change reference.
When configuring a Runbook input dialog with device scope set to an ADT or Device Group, the dropdown list is limited to approximately 500 entries and offers no search or filter function, making it difficult to select from within larger groups. This enhancement would raise the dropdown display limit and add a search field so that specific devices can be located and selected without scrolling through the full list. Customers managing device groups in the thousands would gain a practical way to configure Runbook inputs accurately and efficiently.
NetBrain currently requires users to remove entries from the Devices to Be Discovered list one at a time, which is inefficient when managing large discovery queues. This enhancement would add a Delete All Entries option to clear the entire list in a single action. Customers managing large-scale discovery operations would benefit from reduced manual effort and faster list maintenance.
L3 path traces can be done using traceroute so the value of NetBrain’s path trace is not in its ability to render L3 path traces visually but to show the underlying L2 path.It would be useful to have a switch/button in NetBrain GUI and also API to render path traces in L2 right away.Currently we can only start an L3 path trace via API and run some device/link checks on the path using a DVT but it’s not of much use given that L2 path is often different from L3 path.With a switch as mentioned above, we could trigger a path trace directly in L2, so the DVT checks applied to L2 links would make much more sense and be more useful for troubleshooting.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.