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'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.
Dynamic Search currently strips special characters, such as '#', from search terms before matching, causing the search to return results based on the remaining substring rather than the exact term entered. This enhancement proposes updating Dynamic Search to preserve special characters during matching so that a term such as 'link#' returns only exact matches rather than all results containing 'link'. Customers searching for device or interface names that include special characters would receive precise results and avoid manually filtering out unrelated matches.
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.
Hostname matching used in batch and site definitions is currently case sensitive, so devices whose hostname casing differs from the defined criteria can be excluded even when a definition is intended to cover all devices. This causes benchmark queries scoped to 'All Devices' to omit devices unexpectedly, without any indication to the administrator that a case mismatch is the cause. This enhancement would make hostname matching case-insensitive across batch and site definitions used in Benchmark and related queries. Customers would gain more reliable and predictable device coverage in their benchmark and discovery operations without needing to manually verify hostname casing.
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.
NetBrain's discovery and benchmark drivers for Cisco IOS Switch, Cisco Router, and Cisco SD-WAN Router devices currently issue the standard 'show running-config' command, which does not return default or implicit configuration parameters that some configuration assessment workflows require. This enhancement would introduce a driver option to retrieve configuration using 'show running-config all' instead, configurable so that it persists reliably across patches and upgrades and does not affect other tenants or customers in shared environments. Customers who rely on configuration assessment rule sets that depend on complete configuration detail, including default values, would benefit from consistent and accurate results without needing manual driver modifications after each upgrade.
Network Intent currently supports diagnostic checks based on CLI command output and parsed device data, but it cannot issue an API call to an external system and use the returned response as part of its diagnostic logic. This enhancement would extend Network Intent to support API-based calls as a step within an intent, allowing the returned data to be evaluated and incorporated into the overall diagnostic assessment. Customers integrating with external systems, such as monitoring platforms or ticketing tools, would gain a more complete and automated diagnostic workflow without needing to build custom logic outside of Network Intent.
Summary Dashboards currently aggregate device data at the site level but do not provide a way to select or exclude individual devices within that aggregated view. Users who want to focus on a subset of devices at a site must rely on the full aggregate result, with no mechanism to narrow the displayed devices. This enhancement would add a device selection filter, such as a checkbox list, to site-level summarization widgets so users can choose which devices to include in the displayed results. This would give customers more granular control over site-level reporting, allowing them to focus on relevant devices without needing to build separate dashboard configurations.
When multiple Seed Network Intent instances generate CSV export files, the system currently assigns generic default suffixes such as (1) and (2) to distinguish files, rather than identifying them by device name. This makes it difficult for users to determine which exported file corresponds to which device without opening each file individually. This enhancement proposes allowing users to customize the export file naming convention so that the device name, rather than a generic numeric suffix, is used to differentiate CSV files generated by each Seed Network Intent instance. Customers managing environments with a large number of Seed Network Intents would benefit from being able to quickly identify and organize exported reports without manually opening files to determine their source device.
NetBrain currently displays the underlying database name, rather than the configured domain name, in report notifications generated by QApp. This can create confusion for administrators who manage multiple domains, since the notification does not reflect the domain's intended identity. This enhancement proposes that QApp report notifications reference the domain's display name instead of its internal database identifier. Ensuring accurate domain labeling in these notifications would reduce confusion and support overhead for customers operating multi-domain environments.
NetBrain discovery currently does not support authenticating to devices using SSH public key credentials; only standard username and password based authentication is supported for establishing device sessions during discovery. This enhancement would allow administrators to configure and apply SSH key-based authentication (including specifying a private key file) as a valid credential method for device discovery. Customers whose network devices are configured to require or prefer public key authentication would be able to complete discovery successfully without falling back to less secure or unsupported authentication methods.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.