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 does not currently retain the underlying command output within Network Intent results when the intent is executed in bulk or through a scheduled task, even though this output is available when the intent is run interactively on a single device. This enhancement would preserve and expose the command output associated with each device in bulk and scheduled Network Intent executions, consistent with prior product behavior. Retaining this data would allow operations teams to review the exact basis for diagnosis or troubleshooting outcomes after large-scale or unattended runs, rather than only seeing final results without supporting detail.
Configuring Azure SSO external authentication currently requires administrators to follow a multi-step manual process that can be difficult to complete correctly without close guidance. This enhancement would introduce a more guided, streamlined configuration workflow for setting up Azure SSO, such as clearer in-product steps or validation checks during setup. Customers implementing SSO would benefit from reduced configuration errors and faster, more reliable deployment of external authentication.
NetBrain currently does not support scheduling a Network Intent to run repeatedly at a fixed interval within a defined daily time window; existing scheduling options only allow a single run time or basic recurrence, without the ability to specify a start and end time paired with an execution frequency. This enhancement would allow users to configure a Network Intent to execute automatically at a set interval (such as every hour) between a defined start and end time each day. Supporting this level of scheduling granularity would reduce the need for manual intent execution during business hours and enable more consistent, hands-off monitoring throughout the day.
The Tenant Management list and the Front Server Controller list do not display their entries in alphabetical order, requiring administrators to scan unsorted lists to locate a specific tenant or front server. This enhancement would apply alphabetical ordering to both lists so that entries are easier to locate. Customers managing environments with many tenants or front servers would benefit from reduced time spent searching these lists and a more consistent administrative experience.
When a QAPP consumes a path attribute variable for an interface, such as the inbound interface used to build a command like packet-tracer, the system currently returns both L2 and L3 interfaces for that path node. This produces inaccurate command input and increases QAPP run time when many L2 interfaces are present, since only the single L3 interface displayed on the map is relevant. This enhancement would allow QAPPs to reference the L3 topology interface exclusively when resolving path-based interface variables, matching what is shown on the map. This would improve the accuracy of automated command execution and reduce unnecessary processing time for customers running diagnostic or remediation QAPPs against path attributes.
The global search results window currently displays results in a fixed, limited-size window, requiring users to scroll left and right to review full result details. This enhancement proposes allowing the search results window to be expanded or resized so that more content is visible at once. Customers analyzing search results would benefit from improved readability and efficiency, reducing the need for repetitive scrolling during review.
NetBrain currently does not provide device-level logs for scheduled parser tasks, leaving users unable to determine which specific devices failed during a scheduled run. This enhancement would generate a detailed log or report for each scheduled parser task execution, listing per-device parsing status and any associated errors. Providing this visibility would allow customers to quickly identify and troubleshoot failed devices without needing to manually investigate or re-run the parser task.
The search field currently interprets a partial IP address entry, such as 10.1.1.1, as a range match and returns all addresses within that range, such as 10.1.1.1 through 10.1.1.199. There is no way to instruct the search to return only the exact address entered. This enhancement proposes adding an exact-match search modifier, such as a trailing underscore character, that restricts results to the precise IP address typed rather than an inferred range. Customers searching for a specific device or interface by IP would locate the correct result more quickly and avoid manually filtering through unrelated range matches.
NetBrain currently applies the 'Only keep data in the last X days' cleanup setting on a per-user basis, which results in inconsistent data retention periods and cleanup reminder prompts across different users within the same organization. This enhancement would allow administrators to configure the retention period as a single global setting applied uniformly to all users, and would clarify the reminder message to state when old data will be removed and when the next reminder will appear. Customers managing shared environments would benefit from consistent data retention behavior and reduced confusion caused by conflicting per-user configurations.
Service Monitor currently requires an administrator to log in and manually identify and remove aged data records, with no mechanism to detect or purge data once it exceeds a defined age automatically. This enhancement would allow Service Monitor to automatically detect data that has aged past a configurable threshold and delete it without requiring manual review or action. Customers would benefit from reduced administrative overhead and more consistent data hygiene, particularly in environments where aged data accumulates frequently and manual cleanup is not sustainable.
NetBrain currently displays a fixed 'SITE' label on the cloud icon within site maps, with the site description rendered separately below the icon, and administrators have no way to customize the text shown directly on the cloud icon. This enhancement would allow administrators to edit or configure the label text displayed on the site cloud icon itself. Providing this flexibility would let customers align map labeling with their own naming conventions, improving clarity and consistency when reviewing site maps.
NetBrain currently represents Cisco Catalyst switches configured as Virtual Switching System (VSS) or StackWise Virtual as a single logical device on the map, even though the underlying chassis are physically separate and, in some deployments, installed in different locations connected only through standard front-panel ports. This enhancement would allow the two chassis in a VSS or StackWise Virtual pair to be displayed as two linked device representations on the map, connected via the inter-switch link, with data such as MAC, ARP, and routing information collected from the active member and mapped to the appropriate chassis based on module-specific port naming. Device naming would use a stable suffix indicating chassis membership rather than an active/standby designation that can change over time. This would give customers an accurate physical topology view for stacked switches, supporting correct link visualization and easier troubleshooting when chassis members reside in different physical locations.
Service Monitor currently displays a status banner indicating that the Service Monitor Agent has been stopped, and this banner is visible to all users regardless of role. Standard, non-administrative users who have no ability to act on this information may see the banner and mistakenly believe the application is malfunctioning. This enhancement would restrict visibility of the Service Monitor Agent status banner to administrator users only, or provide a configurable setting that allows administrators to control which user roles see this notification. Limiting banner visibility to users who can act on the information would reduce unnecessary support inquiries and prevent confusion among standard users when services are intentionally stopped for maintenance or performance reasons.
NetBrain currently displays a Virtual Switching System (VSS) or similarly stacked chassis configuration as a single device icon on the topology map, even though the underlying deployment consists of two or more physically stacked switches. This limits the accuracy of site topology visualization for customers who rely on the map to reflect actual physical device counts and connections. This enhancement would introduce a way to represent stacked chassis configurations more accurately on the map, either by rendering each member chassis as a separate connected device or by using a distinct icon that clearly indicates a device stack. Customers would benefit from improved topology accuracy, which supports better network documentation and troubleshooting for environments that rely on virtual switching stacks.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.