NetBrain Feature Requests
Browse, vote, and track the status of feature requests from the NetBrain community
Open
Browse open ideas available for voting, feedback, and discussion.
On the Roadmap
View ideas that are planned for future product development.
In Development
Explore ideas that are currently being developed by the product team.
Available
Explore ideas that are now available in the product.
Not Planned
View ideas that are not currently planned for product development.
Filter by idea status
Filter by features
1146 Ideas
Discover Standby APIC Controllers in ACI Fabric TopologyOn the Roadmap
NetBrain's ACI discovery process currently identifies active APIC controllers within a fabric but does not detect or display standby APIC controllers in the network tree, even when a fabric spans multiple pods with a designated standby node. This enhancement would extend SDN discovery logic to recognize standby APIC controllers and represent them alongside active controllers in the topology view. Full visibility into APIC redundancy status helps customers confirm fabric resiliency and quickly identify controller-level issues without relying on manual verification outside NetBrain.
Automated User Account Deprovisioning Synced with TACACS+On the Roadmap
NetBrain currently creates user accounts automatically upon first successful TACACS+ login, but it provides no corresponding mechanism to remove or deactivate those accounts when the associated user is deleted from TACACS+. Administrators must identify and remove unused accounts manually. This enhancement would introduce a scheduled process that checks NetBrain user accounts against TACACS+ to confirm continued existence, and automatically deactivates or removes accounts that are no longer present after a configurable inactivity period. This would reduce the administrative burden of manual account audits and lower the security risk associated with orphaned or stale user accounts.
Support bidirectional path calculation through Internet Cloud and MPLS L3 Cloud objectsOpen
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.
Display physical interface names in L2 topology instead of interface aliasOn the Roadmap
L2 topology maps currently display the configured interface alias (such as a firewall nameif value like 'inside') rather than the underlying physical interface name. This makes it difficult to correlate the L2 map with physical cabling and hardware-level troubleshooting, since the alias does not reveal which physical port is in use. This enhancement would allow L2 topology to render the physical interface name (e.g., ge0/1, ge0/2) alongside or in place of the interface alias, without requiring any change to L3 topology behavior. Providing accurate physical interface labeling in L2 maps would improve troubleshooting efficiency and give customers clearer visibility into physical connectivity, particularly for devices that use custom or logical interface naming conventions.
Automatic Tag Inheritance for Device GroupsOpen
NetBrain currently requires users to manually assign Layout Tags to individual devices, even when those devices belong to a defined device group. When a device group's membership changes, such as new devices being added or existing devices removed, the associated tags do not update automatically, requiring repeated manual effort to keep tagging accurate. This enhancement proposes allowing a Layout Tag to be associated directly with a device group so that any device added to the group automatically inherits the tag, and any device removed from the group has the tag automatically removed. Customers managing large or frequently changing device groups would benefit from consistent, up-to-date tagging without ongoing manual maintenance.
Separate Notification Controls for Discovery Task Failures and New Device DetectionOn the Roadmap
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.
Default External Authentication Template for New Tenants/DomainsOn the Roadmap
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.
Email Alert Notification for Scheduled Plugin FailuresOn the Roadmap
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.
Filter to Display Only Versions with Detected ChangesOn the Roadmap
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.
Plain-Text Copy and Unified Diff Export for Compare ResultsOpen
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.
Cross-Tenant Replication of Vendor Model Table SettingsOn the Roadmap
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.
Continuous Health Monitoring Dashboard for Non-Technical StakeholdersOn the Roadmap
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.
Increase execution limit for API-triggered Qapp/DVT live data retrievalOpen
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.
Option to Exclude Site Map NBR Page from Scheduled Visio ExportOn the Roadmap
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.
Default Downward Tree Layout for Site MapsOn the Roadmap
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.
Enhanced Debugging Tools for QApp Python ScriptingOpen
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.
Global Default Setting for Site Map Layout and Link VisibilityOpen
NetBrain currently requires administrators to manually configure map layout and link visibility settings, such as switching to a downward tree layout or hiding Layer 2 links, on a site-by-site basis. In environments with a large number of sites, this manual process is time-consuming and prone to inconsistency across the site map hierarchy. This enhancement would introduce a global, admin-configurable setting that allows a defined map layout style and link visibility rules to be applied consistently across all site maps at once, rather than requiring individual site-level adjustments. This reduces manual configuration effort, ensures visual consistency across large site map hierarchies, and lowers the administrative burden for customers managing extensive network topologies.
Reporting for API Trigger Automation Manager CallsOn the Roadmap
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.
Prevent and clean up empty Runbooks attached to mapsOn the Roadmap
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.
Streamlined Change Control Workflow for Ansible-Based RunbooksOpen
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.
Enhanced Detail in Audit Log Entries for Configuration ChangesOpen
The audit log currently does not provide sufficient detail to identify the exact nature of a change made within the system, making it difficult for administrators to trace specific modifications. This enhancement would expand audit log entries to capture granular details of each change, such as the specific field, setting, or configuration element affected and its before-and-after values. Administrators would benefit from improved visibility into system changes, supporting faster troubleshooting and more accurate compliance and change management reviews.
Filter by features
- All features
- AI
- Automation
- Benchmark
- Change Management
- Data Management
- Digital-Twin
- Installation&Deployment
- Integration
- Live Access
- Map
- Multi-Vendor Support
- NetBrain API
- Others
- Path
- Runbook
- System Health Monitoring
- System Management
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain UniversityEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.