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.
Dashboards currently support splitting data only by Device Site or Device Group, which limits how users can categorize and view alert data. When Device Groups are misconfigured or contain overlapping device membership, alert counts can be skewed or duplicated across groups, reducing the reliability of dashboard reporting. This enhancement would add native split options for Device Type and Geolocation, allowing users to categorize dashboard data along these dimensions without relying on manually maintained Device Groups. Customers would gain more accurate and flexible dashboard views, reducing the risk of misleading alert counts and simplifying dashboard configuration for organizations that categorize their network by device type or physical location.
Summary Dashboards currently display multiple independent numeric metrics per group, and when these roll up into executive-level views, the resulting large set of numbers can be difficult to interpret at a glance. There is no option to hide unnecessary metrics or to present health status through visual indicators rather than raw counts. This enhancement would allow summary metrics to be configured for visibility, including the ability to show, hide, or remove specific metrics, and would introduce visual summary widgets such as pie charts for success versus failure, bar or stacked bar charts for alert distribution, and trend arrows for status change over time. Executives and management-level stakeholders would gain a faster, more intuitive understanding of group-level health without needing to interpret dense numeric displays.
Dashboards currently ingest entire Golden Intent objects in full, including every diagnosis block they contain, without a way to isolate only the blocks relevant to a specific workflow. This enhancement would allow users to select specific diagnosis blocks from a Golden Intent and apply keyword or tag-based filtering, such as config drift from baseline, config drift from reference, state check, or config check. Customers running Config Drift workflows would be able to surface only the diagnostic results relevant to their use case, improving dashboard clarity and reducing noise from unrelated diagnosis blocks.
Observability dashboards currently incorporate all intent dashboards associated with a rule automatically, and administrators must rely on ADT-based selection to manage which intents appear, a method that does not scale well in large environments and is prone to error due to truncated intent column names. This enhancement would introduce a dynamic, searchable interface for selecting intent dashboards, with support for grouping by feature, intent type, and vendor. Customers managing large or evolving environments would benefit from reduced manual effort when new designs or vendors are introduced, along with more accurate and scalable dashboard configuration.
NetBrain currently adds discovered devices directly into the active inventory and applies them toward the licensed device count as soon as discovery completes, without an intermediate verification step. This enhancement would introduce a holding tank for discovered devices, allowing an administrator to review and explicitly approve devices before they are added to inventory and counted toward the device license. This capability would give administrators greater control over inventory accuracy and license consumption, reducing the risk of unwanted or unintended devices being counted against the license.
NetBrain currently places several frequently used path discovery options under the Advanced Path Discovery Settings section, where they are easily overlooked by users configuring path behavior. This enhancement would relocate the most commonly used options to the main Path Settings menu, while retaining less frequently used options under Advanced. Improving the visibility of these settings would help customers configure path discovery more effectively without needing to locate options buried in a secondary menu.
Search currently supports lookups by DNS name but does not recognize switchport values, such as a switch and interface identifier, as valid search input. This enhancement proposes extending search functionality to accept switchport values so that users can locate the corresponding device or table entry directly. Customers troubleshooting connectivity by switchport would benefit from faster lookups without needing to cross-reference other tables or rely on alternate identifiers.
Building connectivity network diagrams that depict both primary and secondary paths currently requires manual plotting, which is time-intensive for individual diagrams and significantly more so for consolidated views covering multiple components. This enhancement would introduce automated generation of network diagrams that identify and display both primary and secondary connectivity paths for each connection, reducing reliance on manual layout work. Customers who must produce accurate connectivity diagrams for audit and project documentation purposes would gain substantial time savings and more consistent, repeatable diagram output.
NetBrain currently does not populate the Runbook Document with results from all scheduled executions of an Intent when that Intent is configured to run multiple times at a defined interval; only the first execution's result is captured, even when the 'Last results' or time-window based result settings are configured. This enhancement would update Runbook Document generation to honor the configured result retention settings and include the results from every scheduled execution of the Intent, consistent with how manual multi-run executions are already captured. Providing complete execution history in the document would give operations teams full visibility into all scheduled diagnostic results for review, reporting, and audit purposes.
NetBrain does not currently support auto-remediation within the traditional Automated Data Table (ADT) environment, limiting this capability to newer table formats. This enhancement would extend auto-remediation functionality to traditional ADTs, allowing it to be configured and executed using the same workflow customers already use. Customers who rely on the traditional ADT interface would gain access to automated remediation without needing to migrate existing tables or adopt a new workflow.
The Topology Manager currently does not display VLAN, media type, or VRF information for device interfaces, which limits a user's ability to identify the correct interface when manually establishing a link between devices. This enhancement would add VLAN, media, and VRF attributes to the interface details shown within the Topology Manager, allowing users to reference this context directly while creating manual connections. Customers working in environments with overlapping VLANs or multiple VRFs would benefit from more accurate manual link creation and reduced reliance on external data sources to confirm interface context.
The API parser currently applies a fixed data size limit of approximately 2MB when receiving payloads from custom API adapters. When the data passed to the parser exceeds this threshold, the parser returns a truncated string rather than the complete payload, with no option to adjust the limit. This enhancement would make the API parser data size limit a configurable setting, allowing administrators to raise the threshold to match their integration needs. Customers building custom API adapters that return larger data sets would be able to process complete responses without truncation or the need for workarounds that split data into smaller chunks.
When a user identifies a device by an IP address during troubleshooting and initiates a Smart CLI login, the session currently connects using the IP address that was entered, rather than the MGMT IP configured for that device in Shared Device Settings. This can result in login attempts against an unintended interface when the entered IP differs from the device's designated management address. This enhancement would allow Smart CLI to log in using the MGMT IP stored in Shared Device Settings for the identified device, either by default or through a selectable option to choose which IP address is used for the connection. Customers would benefit from more reliable and consistent device access during troubleshooting, since login behavior would align with the management IP intended for administrative access rather than the IP address used only to identify the device.
The Smart CLI device search currently requires users to type an exact or partial contiguous string to locate a device, without support for wildcard characters such as an asterisk to represent any sequence of characters. This enhancement would add asterisk-based wildcard matching to the Smart CLI device search field, consistent with the pattern-matching behavior found in common network automation consoles. Customers managing large device inventories would benefit from faster, more flexible device lookup, reducing the time spent scrolling or typing exact names when initiating a Smart CLI session.
NetBrain currently provides no in-product explanation for why Intent Diagnosis results may fail to save during Proactive Automation (PA) executions, leaving customers without context when this scenario occurs. This enhancement would add guidance to the Help Icon describing the common causes of Intent Diagnosis results not saving during PA executions. Surfacing this information would help customers self-diagnose the scenario and reduce reliance on support engagement for clarification.
In multi-tenant environments, users who are granted the User Management privilege can currently view Applicant List, Existing User List, and Edit User details for all tenants and domains on the platform, rather than only their own. This enhancement would scope the User Management privilege so that a user with this privilege can view and manage only the applicant and user account information belonging to their assigned tenant or domain. This capability would be particularly valuable for MSP deployments, where multiple customers share the same platform and administrators must be prevented from viewing user information belonging to other tenants.
When using a CSV within Network Intent, a static value referenced by the CSV currently must be entered separately in each diagnosis that uses that CSV, with no mechanism to define it once and have it apply universally. This enhancement proposes allowing a static value to be configured a single time for a given CSV and automatically reflected wherever that same CSV is referenced across diagnoses. Customers managing multiple diagnoses built on shared CSV data would benefit from reduced manual configuration effort and lower risk of inconsistent values across related intents.
NetBrain currently does not provide a way for administrators to designate which data collection method, CLI or API, should serve as the authoritative source when both are configured for a device. When the two sources report conflicting values for items such as configuration content, serial number, or interface status, the platform has no defined precedence rule, which can lead to inconsistent or inaccurate data being displayed or used in downstream tasks. This enhancement would add a global setting that lets administrators specify a primary data source, either CLI or API, with the secondary source used automatically only when the primary source is unavailable or fails to return data. Customers operating hybrid environments with both CLI and API-managed devices would gain more predictable data accuracy and reduced troubleshooting effort tied to source conflicts.
NetBrain currently does not map the internal tunnel topology within Cisco ACI fabrics, and A-to-B path calculation does not account for these tunnels when computing a path. This enhancement would add discovery and visualization of ACI fabric tunnels on topology maps and extend path calculation logic to incorporate these tunnels as part of the computed path. Customers operating ACI environments would gain more complete topology visibility and more accurate end-to-end path results, reducing the need for manual verification of tunnel-based connectivity.
NetBrain currently locks the visual attributes of a connection line, such as weight, style, and color, once that line is linked to a device or interface object, forcing all linked lines to display with the same default appearance. This enhancement would allow users to customize the weight, line style, and color of linked connections while preserving the underlying link to the source object. Providing this flexibility would let customers visually differentiate network architectures directly on linked maps without sacrificing the maintainability benefits of object-linked connections.
NetBrain currently requires users to manually supply macro variable input separately for each device when running auto-intent across multiple devices on a map, even when the same value applies to every device involved. This enhancement would allow a single macro variable input to be entered once and automatically applied to all devices selected on the map during auto-intent execution, eliminating the need for repetitive per-device entry. Customers running auto-intent workflows against large device sets would benefit from reduced manual effort and faster execution of automated diagnostics.
NetBrain's ServiceNow Automation integration currently transfers only error messages, giving users no visibility into informational or status messages generated during automation. This enhancement would transfer all automation messages to ServiceNow and add a GUI filter that lets users choose to view all messages or narrow the view to error messages only. Customers with different monitoring preferences would benefit from this flexibility, allowing teams focused on error triage to keep a filtered view while other users retain full visibility into automation activity.
NetBrain currently only allows a Network Intent to decode all devices in a run, even when only a subset of devices failed decoding on the previous attempt. This forces unnecessary reprocessing of devices that already decoded successfully whenever a retry is needed. This enhancement would add an option to decode only the devices that failed in the last attempt, leaving the decode status of previously successful devices unchanged. Limiting reprocessing to failed devices would reduce unnecessary system load and shorten the time required to complete large-scale intent runs.
NetBrain currently only allows administrators to set a password on a site map one at a time through the UI, which becomes time-consuming for organizations managing a large number of maps. This enhancement would introduce the ability to select multiple site maps and apply a password simultaneously in a single bulk action. This reduces administrative overhead and helps ensure that all maps in a large inventory are consistently protected from unauthorized modification.
NetBrain's current DataView/QApp scheduling interface presents the repeat interval and repeat count in a way that can be misread, making it appear that the job will run a set number of times within a short window rather than running periodically over a longer duration. This enhancement would revise the scheduling UI to clearly separate and label the interval value and the repeat count, similar to the clearer presentation used in earlier product versions. Improving this clarity would reduce user confusion about how scheduled DataView and QApp tasks will actually execute and help customers configure schedules with confidence.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.