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 provides no visibility into the progress or status of an Intent execution triggered from an Automated Data Table (ADT). Users must manually rebuild the table to determine whether results are complete, which becomes impractical for large ADTs with many devices. This enhancement would add a status or progress indicator that reflects the execution state of each Intent triggered from an ADT, allowing users to monitor completion without repeatedly rebuilding the table. This would reduce wait time and uncertainty for users running large-scale preventive automation checks, particularly in environments with sizable device inventories.
NetBrain currently requires administrators to manually lock the Shared Device Settings flags for each device after discovery completes, with no option to apply this automatically. This enhancement would introduce a configuration option to automatically lock Shared Device Settings once a device is successfully discovered. This would reduce manual administrative effort and help ensure device configuration settings remain protected immediately after discovery without requiring follow-up action.
NetBrain currently does not provide a way to automatically copy or sync saved maps to an external cloud storage location. This enhancement would allow maps to be automatically saved to a customer-configured Azure Blob Storage container whenever they are created or updated within NetBrain. Customers would benefit from an additional layer of backup and off-platform retention for their network maps without requiring manual export steps.
NetBrain Incident Quick Access currently does not display a reference to the associated ServiceNow incident or ticket number. This enhancement would add the ServiceNow ticket number as a visible field within the Incident Quick Access interface. Surfacing this reference would allow users to quickly correlate NetBrain incidents with their corresponding ServiceNow records, improving cross-tool traceability during incident investigation.
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.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.