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
835 Ideas
Automatic Execution and Save for Runbook Document NodeOpen
Today, the Document node within a Runbook must be manually triggered each time to generate and save the resulting Word document, requiring user intervention at every execution. This enhancement would allow the Document node to automatically execute and save the generated document to a specified location as part of the Runbook run, without requiring a manual step. Customers running Runbooks on a recurring or scheduled basis would benefit from consistent, hands-free documentation generation, reducing manual effort and the risk of missed or delayed document creation.
Collapsible Diagnosis Messages in ServiceNow NetBrain TabOpen
NetBrain currently displays Diagnosis result messages in full within the ServiceNow ticket integration tab, regardless of message length, which can present more detail than some support tiers require at a glance. This enhancement would allow long diagnosis messages to be collapsed by default within the ServiceNow tab, with an option to expand and view full details on demand. Providing this control would help support teams, particularly L1 NOC staff, review ticket information more efficiently without being overwhelmed by lengthy diagnostic text.
Controllable Interface Highlight Logic for Network Intent Data ViewOpen
NetBrain's current Data View logic for Interface Highlight and Data Unit forces display of interfaces that do not belong to the active map, and triggering AutoNI can disrupt a user's existing map layout as a result. This enhancement would make the Highlight and Draw Interface logic configurable so that interface display behavior can be controlled and does not override or alter a map the user has already built. Providing this control would give customers predictable map behavior when running Network Intents and AutoNI, preventing unintended disruption to existing topology views.
Configurable Display Limit for Map Intent ResultsOpen
NetBrain currently limits the map view to displaying a maximum of four entries per intent result, requiring users to click an additional menu to see remaining entries when more results exist. This enhancement would introduce a configurable setting to increase the default number of entries shown on the map. Customers running diagnostic or compliance checks with larger result sets would gain immediate visibility into complete output without extra manual steps, improving efficiency during troubleshooting and validation workflows.
Network Intent Replication Scope Based on API Server Manager Managed DevicesOpen
For Network Intents built using an API Parser, replication currently follows the traditional device-scope model rather than accounting for the devices actually managed through API Server Manager. This enhancement would extend replication logic so that the scope of an integrated Network Intent is determined by the Managed Devices configured in API Server Manager. Aligning replication scope with the API-managed device list would ensure intents replicate correctly to the devices the API Parser applies to, reducing gaps or mismatches for customers relying on API-based integrations.
Custom Subfolder Organization for Network ChangesOpen
NetBrain currently does not support organizing Network Change records into custom subfolders, requiring users to manage all changes within a single flat list regardless of site, equipment type, or status. This enhancement would allow users with appropriate permissions to create, rename, and manage custom subfolders, and to move Network Changes between them for organizational purposes. Customers managing a high volume of network changes would benefit from faster navigation and clearer categorization of active, completed, and test changes.
Front Server-to-Device Latency Metric During Data CollectionOpen
NetBrain currently measures only the time required to complete data collection from a device, without capturing the network latency between the Front Server and that device. This enhancement would add latency as a collected metric during each data collection cycle, alongside existing timing data. Providing this visibility would help administrators distinguish between slow data collection caused by device processing versus network latency, supporting faster troubleshooting and more accurate performance monitoring.
Device Type Access in API Parser Formula ColumnOpen
NetBrain's API Parser formula column currently does not provide a way to retrieve the device type or other customizable device attributes when transforming data collected from third-party systems. As a result, users cannot apply device-specific formatting logic, such as adjusting interface naming conventions to match NetBrain's interface rules, without manual intervention. This enhancement would add the ability to reference device type or other selectable device attributes within the formula column, enabling conditional data formatting rules based on device-specific criteria. Customers integrating third-party data sources would benefit from more reliable and automated data formatting, easing deployment of integration use cases across varied device types.
Add Last Successful CLI and SNMP Timestamps to Data Accuracy Resolution TableOpen
The Data Accuracy Resolution table currently does not display the date and time of the last successful CLI or SNMP retrieval for each device, making it difficult to identify devices that are no longer reachable or actively monitored. This enhancement would add last successful CLI and last successful SNMP timestamps as dedicated columns within the table. Administrators would gain the ability to quickly identify stale or decommissioned devices for removal from the domain and streamline troubleshooting of device monitoring issues.
Discovery and topology mapping support for Palo Alto Prisma Access (SASE) remote networks and GlobalProtect cloud VPNOpen
NetBrain discovery currently stops at the on-premises edge device (such as a Prisma SD-WAN ION or Panorama-managed firewall) and does not extend topology mapping into Palo Alto Prisma Access cloud infrastructure. As a result, the peer side of IPsec tunnels, BGP peer relationships, and remote network topology hosted within Prisma Access remain unmapped, leaving the path incomplete for both site-to-site and GlobalProtect SaaS-based VPN client connections. This enhancement would add discovery support for Prisma Access remote networks and Prisma-based GlobalProtect VPN through available cloud APIs, enabling NetBrain to retrieve tunnel peer, BGP, and routing details from the Prisma Access side and stitch this information into the existing topology map. Customers operating hybrid environments with Palo Alto SASE architecture would gain complete end-to-end path visibility for both office and remote user connectivity, reducing reliance on manual topology stitching and improving troubleshooting for VPN performance and connectivity issues.
License-Efficient Cross-Domain Path Analysis for Shared Leveraged DevicesOpen
NetBrain currently requires devices that are already discovered and managed in a shared leveraged domain to be separately discovered and licensed again within each individual customer domain in order to support end-to-end path analysis. This duplication results in unnecessary license consumption when the same underlying devices are common across multiple customer environments. This enhancement would allow devices already discovered in a shared leveraged domain to be referenced or linked into individual customer domains for path calculation purposes without requiring separate device discovery and licensing in each domain. Service providers and MSPs managing multiple customer domains that traverse common shared infrastructure would benefit from reduced license consumption while retaining full path analysis capability.
Native Automated Failover to DR Front Server ControllerOpen
NetBrain does not currently provide a native mechanism to automatically redirect Front Servers to a Disaster Recovery Front Server Controller when a failover event occurs, requiring administrators to manually reconfigure Front Server settings and address related items such as SSL certificate updates during the transition. This enhancement would allow a DR Front Server Controller to be defined directly in the Front Server configuration file, with the primary controller able to automatically signal a failover event so Front Servers can reconnect to the DR controller without manual reconfiguration. Customers operating Disaster Recovery architectures would benefit from a simplified, push-button failover process that reduces manual effort and downtime risk during DR events.
API Source Type Support for Cisco DNA Center (Catalyst Center) as a ControllerOpen
NetBrain does not currently support Cisco DNA Center (Catalyst Center) as an API source type, which prevents customers from retrieving and monitoring information available through that platform's API. This enhancement would add Cisco DNA Center (Catalyst Center) as a selectable controller source within API Server Manager, enabling scheduled API calls to retrieve data such as VLAN mismatch status and other diagnostic information not surfaced through the native GUI. Customers operating Cisco DNA Center environments would gain the ability to proactively monitor and report on conditions that currently require manual review, improving operational efficiency and issue remediation timelines.
API Source Type Support for Cisco Catalyst Center as a ControllerOpen
NetBrain currently does not support Cisco Catalyst Center as a controller type for device discovery, which limits visibility into environments managed through this platform. This enhancement would add Cisco Catalyst Center as a selectable API source type within API Server Manager, enabling discovery and modeling of devices managed through it. Customers operating Cisco Catalyst Center environments would gain full network visibility without relying on manual workarounds outside NetBrain.
SCP and Scriptable SSH Client Support for Device Configuration and Firmware ManagementOpen
NetBrain does not currently provide a built-in SCP client for uploading and downloading device configuration files or performing firmware upgrades, nor does it offer a scriptable SSH client for automated device interaction. This limits the platform's ability to manage devices that rely on SCP and scripted SSH workflows, such as networked UPS systems, within a single tool. This enhancement would add native SCP client functionality alongside a scriptable SSH client, enabling automated configuration backup, restore, and firmware upgrade tasks directly from NetBrain. Customers managing large fleets of third-party network-connected devices would benefit from consolidating auditing and configuration management into NetBrain, reducing reliance on custom external scripts and improving operational consistency.
Custom Time Range and Last 1 Month Filter Options for Triggered Automation DashboardOpen
The Triggered Automation dashboard currently limits users to a fixed set of predefined time range filters and does not offer a 'Last 1 Month' preset or the ability to define a custom date range when reviewing task activity. This enhancement would add a custom time range selector along with a 'Last 1 Month' option to the dashboard's filtering controls. Customers managing longer-running automation activity would gain more flexibility to review and analyze task history over the periods most relevant to their operational and reporting needs.
Proxy Support for Front Server Registration with Front Server ControllerOpen
NetBrain's Front Server registration process currently does not honor proxy settings configured at the system or browser level, which prevents Front Servers from completing registration with the Front Server Controller in environments where outbound connectivity requires a proxy. This enhancement would update the Front Server registration workflow to detect and route through configured proxy settings when establishing its connection to the Front Server Controller. Customers deploying Front Servers in proxy-restricted or cloud network environments would benefit from a successful, unattended registration process without requiring manual network reconfiguration or workarounds.
Merge Multiple Network Intent CSV Outputs into a Single Consolidated FileOpen
NetBrain currently generates a separate CSV file for each Network Intent within an Automated Data Table, requiring users to manually open and cross-reference multiple files when reviewing results across different checks. This enhancement would allow the outputs of multiple intents within an ADT to be merged into a single consolidated CSV file. Customers performing configuration drift analysis across multiple features, such as NTP, AAA, banners, and ACLs, would benefit from a unified view of all findings without manual file consolidation.
Convert ServiceNow-Triggered Legacy Automation to Network Intent WorkflowsOpen
NetBrain currently supports ServiceNow change management triggered automation using legacy Gapp and QApp constructs, which operate separately from the Network Intent framework and cannot take advantage of Intent-based capabilities such as diagnosis, reporting, and standardized workflow logic. This enhancement would provide a path to convert or migrate existing Gapp and QApp based automation, triggered by ServiceNow change management events, into equivalent Network Intent workflows. Customers relying on ServiceNow-driven automation would benefit from a consistent, Intent-based automation model that improves maintainability and aligns legacy workflows with current platform capabilities.
Automated Email Alerts for Network Intent Config Comparison Non-ComplianceOpen
NetBrain currently does not support automatically sending an email alert and non-compliance report when a Network Intent template detects a configuration discrepancy, such as a mismatch between startup and running configuration. Users must manually review comparison results within the platform to identify non-compliant devices. This enhancement would allow a Network Intent template to trigger an automated email notification, including a non-compliance report, whenever the defined comparison logic identifies a discrepancy. Customers responsible for configuration compliance would benefit from immediate, proactive visibility into non-compliant devices without needing to manually monitor comparison results.
Scheduled Maintenance Mode to Suspend Live Access for Selected DevicesOpen
NetBrain currently has no mechanism to suspend live access to specific devices during planned maintenance windows, which can result in failed access attempts, false alerts, or interference with ongoing maintenance work. This enhancement would allow administrators to place one or more devices into a Maintenance Mode with a configurable start and end datetime. While a device is within its maintenance window, NetBrain would skip all live access to that device, including scheduled discovery, on-demand CLI, path diagnosis, and runbook execution, then automatically resume normal access once the window expires. Customers performing scheduled device maintenance would benefit from reduced false alerts and fewer disruptions to maintenance activities, along with the convenience of automatic access resumption without manual intervention.
Native path calculation for device-to-VLAN Layer 2 tracingOpen
NetBrain path calculation today supports IP-based, TCP-based, and multicast path types, but does not offer a native path type where the source is a device and the destination is a VLAN for Layer 2 tracing. Customers can approximate this only through a plugin-based workflow that requires manually specifying source device, VLAN, interface, and destination device interface and VLAN, rather than a streamlined native calculation. This enhancement would add a native path type, positioned alongside existing IP and multicast path options, that accepts a source device and destination VLAN and calculates the traversed Layer 2 path across transport technologies such as VPWS, EVPN, Q-in-Q, and standard trunking. Customers operating complex Layer 2 transport environments would gain built-in, consistent path visibility for VLAN-based traffic without relying on plugin workarounds, reducing manual effort during troubleshooting.
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.