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 requires users to manually assign Layout Tags to devices in order to control their placement within a map layout hierarchy; there is no mechanism to derive tags automatically from a device attribute such as Model. This enhancement would allow tags to be generated or assigned automatically based on the device Model field, so that maps can display devices hierarchically by layer according to their model-derived classification. Customers managing environments with a large variety of device models would benefit from consistent, layered map views without the ongoing manual effort of tagging each device individually.
NetBrain currently couples map editing rights and Intent editing rights within the same role construct, such as the 'Shared Resources' role. Administrators cannot grant a user the ability to run Intents and create or edit their own maps without also granting that user the ability to edit Intents themselves, and users without this role cannot edit maps even after receiving explicit edit access from an administrator. This enhancement would introduce independent role permissions for running Intents, editing Intents, and creating or editing maps, allowing administrators to combine these capabilities as needed for each tier of user. Customers with tiered support teams would benefit from finer-grained, least-privilege access control, allowing elevated map access without unintended exposure of Intent editing capability.
Chatbot automation currently requires a user to manually click through each Network Intent Task node during a troubleshooting flow, even in cases where only one candidate device is available for that step. This adds unnecessary time and manual effort to what should be a streamlined automated process. This enhancement would introduce a setting that allows a specified NIT node to execute automatically when it has only one alternative device, removing the need for manual confirmation at that step. Customers running chatbot-driven troubleshooting flows would benefit from faster resolution times and a more consistent end-to-end automated experience.
NetBrain currently does not summarize or display whether a scheduled Network Intent executed as expected on the PAF page, requiring users to manually review each intent individually to confirm execution status. This enhancement would add an alert mechanism and a consolidated execution summary that flags when a scheduled Network Intent did not run as configured. Providing this visibility would allow customers to detect scheduling failures promptly, reducing the risk of undetected data loss and the manual effort of checking each intent's run history individually.
NetBrain currently calculates and displays node license usage in the Domain Summary using logic that may differ from the calculation used for email notifications, which can result in two different license counts being reported to administrators for the same period. This enhancement would align the license count calculation between the in-application summary and notification emails so that both sources consistently report the same value. Ensuring consistent license reporting would reduce confusion for administrators reviewing license capacity and help prevent unnecessary investigation into perceived license discrepancies.
The Summary Dashboard currently does not display the execution time associated with the underlying automation or data collection run, leaving users without visibility into when the displayed results were last generated. This enhancement would add an execution time field to Summary Dashboard widgets, showing users when the data was last refreshed. Providing this information would help customers assess data freshness at a glance, supporting more confident decision-making and more accurate reporting.
NetBrain currently does not provide a way for engineers to observe live CLI output on a device as a configuration change is being executed through Change Management, leaving them without real-time insight into device responses or errors during the process. This enhancement would introduce a read-only CLI console that streams the live command output on the target device while a Change Management task is running, displaying prompts, responses, and any errors as they occur. This would allow engineers to confirm configuration success or quickly identify device-reported issues in real time, reducing reliance on post-execution logs and manual verification steps.
NetBrain currently does not provide a way to export device configuration backups that are approaching the end of their retention period for external storage, nor does it support re-importing previously exported backups back into the system when needed. Customers who wish to shorten their retention window are left without a supported path to retain access to older configuration data. This enhancement proposes adding an export function for historical configuration backups that fall outside a shortened retention period, along with a corresponding restore function to bring externally stored backups back into NetBrain when required. This would let customers reduce on-platform storage retention while preserving the ability to recover and reference older configuration data as needed.
NetBrain's report output for QApp-generated tables, such as Inventory Reports, does not sort correctly on columns that contain numeric values like error counts, even when the underlying field is defined as an integer type. This causes the data to appear ordered as text rather than by numeric value, making it difficult for customers to quickly identify devices or interfaces with the highest error counts. Adding proper numeric-aware sorting for integer and numeric fields in QApp and Inventory Report tables would allow customers to reliably rank and prioritize results by value. This capability would improve efficiency in network health analysis and troubleshooting workflows that rely on ranked error or performance data.
Service Monitor currently has no way to stream or export its critical event and status information, such as a Front Server process no longer running, to external monitoring platforms. Administrators must rely on manual checks within NetBrain rather than receiving this data in their standard operations monitoring tools. This enhancement would introduce a configurable streaming or export mechanism for Service Monitor events, comparable to the existing streaming audit log functionality, allowing critical status changes to be forwarded in a structured format to external monitoring or ITSM platforms. Providing this capability would allow customers to centralize NetBrain health visibility alongside their broader operations monitoring, reducing manual oversight and improving incident response time.
Network Change runbooks currently require target devices to be manually added to each individual node, even when those devices were already specified in the Define Change node. This manual repetition increases the risk that a device is inadvertently omitted from one or more steps in the change process. This enhancement would allow all nodes within a change runbook to automatically inherit the device scope defined in the Define Change node by default, while still permitting manual adjustment where needed. Customers executing multi-step network changes would benefit from reduced setup effort and lower risk of incomplete device coverage across change steps.
NetBrain does not currently provide a way to analyze ARP table entries across the network and summarize which IP addresses are in active use within specific subnets and supernets. This enhancement would add a capability to correlate collected ARP data with defined subnet and supernet boundaries and produce a report of utilized IP addresses for each range. Customers integrating NetBrain with IPAM systems would gain improved visibility into address space usage, supporting more accurate capacity planning and reducing reliance on external tools for this analysis.
NetBrain currently does not notify administrators when the node license count decreases as a result of a license refresh, leaving the change undetected until it affects device monitoring capacity. This enhancement would display a warning message to the user at the time of refresh whenever the node license count has decreased compared to its prior value. Providing this visibility would allow administrators to promptly investigate license changes and adjust node allocations before capacity issues impact operations.
Today, configuring ignored lines or blocks for the Change Analysis Report requires navigating through System Admin, enabling debug mode, and editing individual device driver comparison logic under Tenant Management, a process that involves multiple steps each time a user needs to suppress a false positive. This enhancement would add the ability to configure ignore rules directly within the Change Analysis Report settings, allowing users to manage this behavior in a few steps without accessing System Admin or debug mode. Customers who regularly need to exclude specific lines to avoid false positives would benefit from a faster, more accessible configuration workflow that does not require elevated administrative steps.
NetBrain currently does not provide administrators with a way to review the volume and frequency of API calls made by an individual external integration, nor does it offer configurable controls to rate-limit or throttle excessive API traffic from a specific client. Administrators can only take a reactive step, such as disabling the offending account, when call volume threatens platform performance. This enhancement would add API usage reporting broken down by calling client, showing call counts over daily, weekly, and monthly periods, along with configurable rate-limiting controls that administrators can apply per external API consumer. Customers integrating third-party systems at scale would gain the ability to proactively monitor and constrain API consumption, preserving platform stability without needing to disable an integration entirely.
NetBrain's streaming log server configuration for audit logs currently supports specifying only a single destination IP address, which limits administrators who need to send audit log data to more than one collection endpoint. This enhancement would allow administrators to configure multiple destination IP addresses for the streaming audit log server, either through a dedicated dialog or by accepting a comma-separated list of IPs. Customers who require redundant logging or need to route audit data to multiple monitoring or compliance systems would benefit from this capability without relying on additional workarounds.
NetBrain currently allows users to export results from the Execute CLI Commands node within a Runbook, but the Retrieve Live Data node does not offer an equivalent export option. This enhancement would add an export capability to the Retrieve Live Data node, allowing users to export retrieved results in a manner consistent with the Execute CLI Commands node. Providing this capability would give customers a uniform way to capture and share live data results for documentation and troubleshooting purposes.
NetBrain currently requires administrators to modify the Automated Data Table (ADT) row limitation directly through database command-line access, since no equivalent control exists in the graphical interface. Environments where database tools cannot be installed or accessed require this workaround, creating an inconvenient and less secure administrative process. This enhancement would expose the ADT limitation setting as a configurable option within the NetBrain GUI, allowing administrators to adjust the value without direct database interaction. Customers would benefit from a more accessible and safer administrative workflow, reducing dependency on database tools and specialized technical steps.
NetBrain currently allows a user to manually convert an unknown end system entry into a full End System device without validating whether a matching device record already exists. This can result in duplicate device entries that distort topology maps and complicate network visibility. This enhancement proposes adding a validation step during the manual conversion process to check for existing devices with matching identifying attributes, such as IP or MAC address, before a new device record is created. Customers who rely on accurate topology maps would benefit from reduced manual cleanup and improved confidence in device inventory integrity.
NetBrain's device import process may rely on hostname alone to identify and de-duplicate devices, which can cause conflicts or import failures when multiple domains contain devices sharing the same hostname despite each having a unique fully qualified domain name (FQDN). This enhancement would allow the import process to recognize FQDN as a unique identifier, so devices with duplicate hostnames across different domains can be imported correctly without manual workarounds. Customers managing large, multi-domain environments with overlapping hostname conventions would benefit from accurate, conflict-free bulk device import.
Golden Configuration alert messages are currently static and cannot incorporate match pattern variables from the underlying configuration check, limiting the descriptiveness of the message shown when a check fails. This enhancement would allow customers to define alert message text that references match pattern variables, producing dynamic, context-specific messages for each check. Providing more descriptive alert content would improve visibility and clarity for teams reviewing Golden Assessment results in observability dashboards, reducing the need to cross-reference the underlying configuration to understand the alert context.
NetBrain currently allows highlighting of device icons and interface lines within DVT, but there is no option to visually highlight the associated device or interface level text labels. This limits visibility when scanning maps that contain dense text annotations alongside highlighted elements. This enhancement would add an option within DVT to highlight device and interface text, in addition to the existing icon and interface highlighting. Extending highlighting to text would help customers more quickly identify relevant devices and interfaces during troubleshooting and review, improving overall usability of DVT-based analysis.
The OneIP Table currently displays the port-channel identifier for an IP address when the underlying physical port is bundled into that port-channel, without exposing which physical port is actually carrying the connection. This limits the ability to verify or troubleshoot the physical connectivity associated with an IP entry. This enhancement would extend the OneIP Table to display the physical port information alongside or in place of the port-channel identifier when applicable. Customers who need to verify physical connectivity for troubleshooting or auditing would gain clearer visibility without needing to cross-reference other tools.
NetBrain currently retrieves neighbor information for a site or device on demand each time the Neighbors window is opened, which can result in noticeable load delays, particularly in larger environments. This enhancement would introduce a caching mechanism so that once neighbor data is initially retrieved, subsequent requests for the same information are served from cache rather than triggering a full retrieval each time. Customers working with large topologies would benefit from faster, more consistent response times when repeatedly viewing neighbor information, reducing wait time during troubleshooting and map-building activities.
NetBrain currently does not offer a general method for customers to learn about newly released security patches or software versions outside of individual case updates, and no public-facing listing or subscription service exists for this purpose. This is particularly limiting for customers who operate NetBrain in an offline environment and cannot check for updates directly from their instance. This enhancement would introduce an email subscription option and a corresponding public webpage where customers can view and be notified of all released security patches and new software versions. Providing this capability would help customers meet recurring compliance and security review obligations by giving them a reliable, self-service way to monitor patch and release availability.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.