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 sends discovery task alerts as a single combined notification, covering both task execution failures and newly discovered devices. Teams that only need visibility into new device additions cannot separate that information from operational error alerts, and both alert types are routed to the same recipients. This enhancement would allow administrators to configure discovery alerts as two independent notification types: one for task execution failures and one for newly added device reports, each with its own enable/disable toggle and its own recipient email list. This would let organizations route alerts to the appropriate audience, reducing irrelevant notifications and improving response efficiency for teams with different monitoring responsibilities.
NetBrain currently requires administrators to manually configure External Authentication settings, such as Active Directory group-to-role mappings, each time a new Tenant or Domain is created. This becomes burdensome for organizations that provision large numbers of Tenants or Domains on an ongoing basis. This enhancement would allow administrators to define a default External Authentication template that automatically applies to newly created Tenants or Domains, including group-based access assignments. Customers managing large-scale, frequently changing multi-tenant environments would benefit from reduced manual configuration effort and consistent, immediate access for authorized users upon Tenant or Domain creation.
NetBrain currently does not provide an email notification when a scheduled plugin fails to execute successfully. This enhancement would add an email alert option to the plugin scheduler that triggers automatically upon a failed run. Customers would gain timely visibility into scheduling failures without needing to manually check plugin status, improving operational reliability.
Today, the version or history list for a device displays every captured snapshot regardless of whether meaningful changes were detected between versions, requiring users to manually scan through entries to find relevant ones. This enhancement would add a button or toggle that filters the list to show only the versions where changes were actually discovered. Customers reviewing device history would save time and reduce noise by focusing only on versions that reflect real configuration or state changes.
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.
NetBrain currently requires administrators to manually export the Vendor Model Table from one tenant and import it into each additional tenant or domain to keep OID mappings consistent, which becomes time-consuming as the number of tenants grows. This enhancement would introduce a built-in capability to replicate or synchronize Vendor Model Table changes across multiple tenants directly within the platform, removing the need for manual export and import steps. Customers managing large multi-tenant environments would save administrative effort and reduce the risk of configuration drift between tenants.
NetBrain currently requires an open map and manual runbook execution to view ongoing health status, which limits practical long-term monitoring for users outside the network team. This enhancement would introduce a continuous, always-on health monitoring view that runs indefinitely on a small map without requiring an open session or manual triggers, and would present progress through graphs accessible to non-technical stakeholders. Historical logs of the monitoring output should be retained to support after-action review and root-cause analysis following an outage. This capability would give organizations a simple, persistent way to observe landscape health over time without relying on network specialists to initiate or interpret each check.
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 currently exports the full site map, including the NBR page, whenever a scheduled task updates and exports the map to Visio, and there is no option to exclude specific pages that contain no usable content for the customer's network. This enhancement would allow users to select which pages to include when configuring a scheduled site map export to Visio, or provide a setting to suppress the NBR page from the output. Customers running recurring Visio export tasks would save time by not having to manually remove unwanted pages after each scheduled run.
NetBrain does not currently provide an option to set a downward tree layout as the default arrangement for site maps. This enhancement would allow administrators to configure downward tree layout as the standard default across all site maps. Standardizing this default would improve map readability and consistency, reducing the need for manual layout adjustments each time a site map is generated or refreshed.
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.
NetBrain currently does not provide a report that identifies the purpose or source of API calls triggered within the API Trigger Automation Manager. This enhancement would add a reporting capability that summarizes API call activity, including the intent or context behind each call. Customers managing automated integrations would gain improved visibility into API usage, supporting easier troubleshooting and audit of automation activity.
NetBrain currently allows empty Runbooks, containing no nodes beyond the Start node, to be saved and remain attached to maps, with no mechanism to identify or remove them in bulk. This enhancement would introduce a way to detect and bulk-delete existing empty Runbooks across maps, along with a safeguard that prevents new empty Runbooks from being saved with a map going forward. Customers who rely on frequently accessed maps for critical sites would benefit from a cleaner Runbook list, reducing time spent opening multiple Runbooks to identify the correct one to execute.
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.
Service Monitor currently raises alerts whenever a monitored service is found stopped, even when the service is intentionally offline, such as a standby node in a multi-datacenter deployment. There is no mechanism to mark a service as expected to be in a stopped state so that Service Monitor can suppress alerts for it. This enhancement would allow administrators to designate specific services or devices as intentionally stopped or in standby mode, so that Service Monitor excludes them from triggering alerts while still tracking their status. This would reduce alert noise and prevent unnecessary escalation for customers running high-availability or multi-datacenter architectures where certain services are expected to remain inactive until failover occurs.
NetBrain currently requires users to move device groups into folders one at a time, selecting each group individually from a dropdown menu and choosing a destination folder. Drag-and-drop and multi-select move actions are not supported, which makes reorganizing a large number of device groups into folders a slow, repetitive task. This enhancement proposes adding multi-select capability to the device group list, allowing users to select several device groups at once and move them together to a chosen folder in a single action. This would significantly reduce the time and effort needed for customers managing large numbers of device groups, particularly when reorganizing an environment after adopting a new folder structure.
NetBrain currently does not provide a way to automatically purge or bulk delete triggered maps once they exceed a defined age, requiring users to remove outdated maps manually one at a time. This enhancement would introduce a configurable retention policy or bulk delete option that allows administrators to automatically remove triggered maps older than a specified number of days. Customers generating large volumes of triggered maps through integrations would benefit from reduced manual maintenance and better control over map repository growth.
NetBrain does not currently provide a direct method to identify all switches, trunk links, and access ports associated with a specific VLAN ID and automatically render that information as an L2 topology map. Customers must rely on manual command output review or ad hoc device grouping to approximate this view, which becomes impractical when many VLANs span multiple VRFs and does not reliably capture access port connections. This enhancement would add a capability to specify a VLAN ID and automatically generate an L2 topology map showing all associated switches, trunk interfaces, and access ports. This would give customers an efficient, accurate way to visualize VLAN-scoped L2 topology without manual workarounds, improving troubleshooting and network documentation for environments with a large number of VLANs.
NetBrain currently does not support discovery and mapping of AWS Gateway Load Balancer (GWLB) resources within cloud environments. This enhancement would add native support for GWLB, allowing the platform to discover, model, and represent GWLB endpoints and associated traffic flows in topology maps. Customers deploying GWLB as part of their AWS network architecture would gain complete visibility into their environment without manual workarounds.
NetBrain path trace currently does not allow a VPN-terminating device to be selected as the first-hop gateway when calculating the path for a VPN client, even when that device is the actual point of entry into the network. In environments where multiple gateway-capable devices exist, the path engine may default to an unrelated device, producing an inaccurate path that does not reflect real traffic flow. This enhancement would allow the path trace engine to correctly identify and offer the actual VPN-terminating device as a selectable gateway option for VPN client path calculations, ensuring the resulting path reflects the true routing behavior. Customers relying on path trace for VPN troubleshooting would gain accurate, end-to-end visibility without needing to manually correct or reinterpret an incorrect calculated path.
NetBrain currently does not reliably complete Path node execution when it is included as part of a scheduled network change task, causing the live post-change path to fail to generate. In addition, when both pre-change and post-change paths are captured, the resulting report does not clearly separate or distinguish the two paths from one another. This enhancement would ensure that Path nodes execute consistently within scheduled change workflows and would present the pre-change and post-change path results as distinct, clearly labeled sections in the generated report. Reliable path execution and clear before-and-after comparison would give customers confidence in validating the network impact of scheduled changes without manual follow-up.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.