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 Golden Intent currently does not provide a way to generate a CSV report of configuration comparison results without relying on an external intent, which adds unnecessary complexity for customers seeking straightforward reporting. This enhancement proposes a native CSV export option within Golden Intent that automatically populates Device Name, Golden Configuration, Running Configuration, Missing Lines, and Extra Lines for each device. Customers performing configuration compliance audits would benefit from a direct, simplified export path that removes the need for external intent workarounds and supports faster review of configuration discrepancies.
NetBrain currently does not provide an adapter to discover and model Oracle Cloud Infrastructure (OCI) resources, unlike its existing support for AWS, Azure, and GCP. This enhancement would add a dedicated OCI adapter to enable discovery, modeling, and topology mapping of OCI infrastructure consistent with other supported public cloud platforms. Customers running workloads on Oracle Cloud would gain complete visibility into their multi-cloud infrastructure without relying on manual workarounds.
NetBrain dashboards currently cannot be built using an application path as the organizing structure, even though Automated Data Tables can capture application name, path details, path devices, and related automation results such as ping tests, interface error checks, and device health status. Users must instead construct dashboards from other data groupings, losing the direct association between a dashboard view and the application path it represents. This enhancement would allow dashboards to be created and organized directly around application path data, so that path devices, health checks, and related automation results for a given application can be displayed together in a single view. Customers monitoring application performance across distributed paths would gain a more direct and consolidated way to assess path health without manually correlating separate data sources.
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.
Dynamic Search for the Mgmt IP field currently does not offer a 'Contains' or 'Does Not Contain' operator, limiting users to exact-match style criteria when building Dynamic Device Groups. This enhancement would add 'Contains' and 'Does Not Contain' as selectable operators for the Mgmt IP field in Dynamic Search. Customers managing devices across specific IP ranges or subnets would be able to group devices by partial IP address matches without needing to manually enumerate each address or rely on workarounds.
NetBrain currently does not provide a way to sort Network Intent decode results by time, nor does it surface an aggregate decode success rate across devices. This makes it difficult to identify the most recent decode attempts, especially when troubleshooting live issues across multiple devices, and to assess how many devices are impacted or improved after configuration changes are made in Front Server settings. This enhancement would add the ability to sort decode results by time and display a decode success rate summary, showing how many and which devices succeeded in the latest decode attempt. Customers managing large device inventories would gain faster visibility into current decode health and the impact of configuration changes, reducing the manual effort required to assess decode status across their environment.
NetBrain currently displays the Next Hop IP as static text within data table results, requiring users to manually note the address and search for or add the corresponding neighbor device to the map. This enhancement would make the Next Hop IP field clickable, triggering an action that attempts to add the referenced device directly onto the current map. Customers tracing network paths or troubleshooting connectivity would benefit from a faster, more direct workflow when moving from a data table entry to the corresponding device on the map.
Network Intent input variables currently cannot be defined using data that has already been collected and stored in a Data View through a System Benchmark task, such as an interface CRC value. Users must rely on separate data collection or manual variable definition even when the needed value already exists in an existing Data View dataset. This enhancement would allow Network Intent input variables to be defined directly from Data View columns populated by System Benchmark, enabling reuse of previously collected data without redundant collection steps. Customers who maintain Data Views through System Benchmark would gain a more efficient way to build Intents on top of existing data, reducing setup effort and improving consistency between collected data and Intent logic.
Network Intent does not currently provide a way to skip a condition mid-iteration or to reposition an existing conditional statement within a table iteration loop without manually rebuilding the surrounding logic. This enhancement would add a 'continue' style control-flow option, or alternatively 'Move Left' and 'Move Right' controls, to allow precise repositioning of conditional statements within existing diagnosis rules. Customers maintaining large or complex Network Intents would benefit from being able to adjust logic ordering and skip conditions efficiently, reducing the effort required to rework existing rules when new conditions are introduced.
Network Intent currently does not allow a Name Rule to incorporate a variable value, limiting naming to static text. This enhancement would add an option to insert a parsed or defined variable into the Name Rule field, allowing generated names to reflect dynamic data such as device attributes or environment identifiers. Supporting variables in Name Rule would give customers greater flexibility in organizing and distinguishing intent results across different environments or configurations without manual renaming.
NetBrain's AI Insights currently does not support uploading external documents such as PDF, Word, or PowerPoint files for evaluation within the AI analysis process. This enhancement would add the ability to upload these document formats directly into AI Insights so their content can be incorporated into AI-driven analysis and recommendations. Customers would benefit from being able to combine external documentation with network data, reducing manual effort to consolidate information before AI evaluation.
NetBrain's parser currently requires every enum variable to be defined with a fixed set of meaningful constants, with no built-in way to represent the absence of a value within that set. When a field may or may not contain a matching value, this forces users to build and maintain multiple separate paragraph parsers and merge their results into a single table. This enhancement would allow a 'None' or null option to be included as a valid member of an enum variable's defined constants, so the absence of a meaningful value can be represented directly within the enum. Supporting this would let customers apply constraints consistently on both sides of an enum variable and consolidate parsing logic into a single parser, reducing maintenance overhead and simplifying table construction.
NetBrain currently triggers an alert as soon as a diagnostic condition is met, without a way to confirm that the condition persists over time or to re-check it at defined intervals. This can result in alerts being generated from brief, transient spikes rather than sustained issues. This enhancement would introduce a configurable option to require a condition to persist for a defined duration before an alert is triggered, along with an option to automatically re-evaluate the diagnosis at set intervals. Supporting persistence and interval-based re-checking would reduce false-positive alerts and help ensure that notifications reflect genuine, sustained performance issues.
NetBrain path calculation currently cannot distinguish between two devices that share identical IP configuration, such as a production device and its disaster recovery counterpart, unless the L3 Active path calculation option is enabled. Without that option, the calculation may present a path to a device that does not actually carry the traffic, since it relies on IP-based matching rather than the ARP-derived MAC address that identifies the true next hop. This enhancement would extend the default path calculation logic to check ARP table entries on the previous hop device and use the resolved MAC address to identify the correct next hop, applying this logic even when L3 Active path calculation is not selected. Customers with redundant or DR device pairs sharing the same IP addressing would gain accurate path visualization without needing to enable a more resource-intensive calculation option, reducing troubleshooting time and improving confidence in the displayed path.
NetBrain path calculation currently displays standby (passive) firewall devices in path results even though these devices do not carry live traffic, since failover has not occurred. This can create confusion when reviewing a path, as the standby device appears as an active hop despite not participating in actual traffic flow. This enhancement would allow path calculation to identify standby firewalls and exclude them from the displayed path result, regardless of branch or topology. Customers troubleshooting network paths would gain a more accurate representation of real traffic flow, reducing the time spent distinguishing active devices from standby ones during analysis.
NetBrain's webhook follow-up action currently does not support inserting variable values, such as an OAuth token, into the HTTP headers of an outbound webhook call. As a result, integrations that require token-based authentication in the request header cannot be configured through this mechanism. This enhancement would allow users to reference a variable and pass its resolved value into a custom HTTP header when a webhook follow-up action is triggered. Supporting this capability would enable OAuth-based authentication for third-party integrations, such as ServiceNow, allowing customers to meet their security and compliance requirements while automating incident or change creation from NetBrain diagnostics.
NetBrain currently exports and imports parser-level data within library ZIP files in a readable form, without any mechanism to obscure content that may include customer-specific details embedded in parser definitions. When libraries are reused or modified across environments, this creates a risk that one customer's sensitive information could be inadvertently exposed to another customer. This enhancement proposes applying an obfuscation method, such as a reversible encoding transformation, to parser-level data during library export, with corresponding decoding during import, while preserving the underlying data structure. Customers would benefit from reduced risk of unintended exposure of sensitive information when libraries are shared, transferred, or modified across accounts.
The GES log currently does not display the intent name or execution path associated with each log entry, making it difficult to trace which intent generated a given log line. In addition, there is no option to export the GES log for offline review or sharing. This enhancement would update the GES log to include the intent name and path for each entry, and add a log export function so the full log can be saved to a file. Customers troubleshooting intent execution issues would benefit from clearer log context and the ability to share exported logs with support or team members without manual copying.
The Device Group edit window does not currently display the Dynamic Search criteria used to define group membership, requiring users to export the group to a CSV file to view this information. This becomes time-consuming when reviewing criteria across multiple groups. This enhancement would surface the Dynamic Search criteria directly within the Device Group edit window, similar to how criteria are displayed in the Site Creation window. Customers managing many device groups would benefit from faster, more direct visibility into group definitions without needing to export data.
NetBrain currently requires users to navigate between separate interfaces, the Template Manager and Template Profile Manager, to complete folder and profile creation when templatizing a troubleshooting process, and it also requires Save and Publish to be performed as two distinct actions rather than a single combined step. This fragmented workflow can cause users to lose track of a saved template or abandon the templatizing process altogether. This enhancement would introduce an inline capability to create a folder or profile without leaving the active save workflow, along with a combined Save and Publish action that allows users to select or create a folder and profile in one step. Reducing the number of screens and clicks required would encourage more consistent use of runbook templatization and reduce user frustration during time-sensitive troubleshooting scenarios.
NetBrain Runbooks currently have no native way to search device configuration or command output for a specific text string; achieving this today requires building a custom QApp to query and filter the underlying data. This enhancement would introduce a Search node within the Runbook canvas that accepts a search string as input and returns the devices where the string is found, along with a configurable number of context lines before and after each match, similar to a grep function. Adding this capability directly to Runbook would remove the need for custom scripting, make troubleshooting workflows more self-contained, and support Runbooks that are triggered from external systems as part of an automated process.
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.
NetBrain currently does not preserve the configured data type of an Automated Data Table (ADT) field when that field is referenced within a Network Intent. A field set to the Device type in the ADT is instead evaluated as a string when consumed by the intent, causing a type mismatch. This enhancement would ensure that Network Intent correctly recognizes and preserves the original ADT field data type, including Device type, when referencing ADT values. Maintaining accurate type handling would reduce automation errors and eliminate the need for manual workarounds when building device-type based intent logic.
NetBrain currently does not support discovery and topology mapping of Hitachi Tropos SuprOS gateway devices used to bridge wired switches across an RF wireless mesh network, resulting in broken Layer 2 and Layer 3 topology continuity where a mesh segment sits between two connected switches. This enhancement would add a discovery and benchmark driver for Tropos SuprOS gateway devices, enabling NetBrain to identify these devices and correctly map the mesh-connected links on topology maps. Customers operating wireless mesh backhaul networks would gain continuous, accurate end-to-end topology visibility across mesh segments without relying on manual link creation or workarounds.
NetBrain does not currently provide a way to test connectivity from multiple Front Servers to a defined set of target devices and report the results of ping, SNMP, and CLI (including login) checks in a single view. This enhancement would add a connectivity test report that lets a user select a device list, group, or CSV of devices, run ping, SNMP, and CLI tests from each available Front Server to those devices, and view the pass/fail results per Front Server and device. Customers undergoing network migrations or infrastructure changes would benefit from being able to validate which Front Servers can reach which devices ahead of time, helping ensure uninterrupted communication and reducing the risk of unexpected connectivity loss during and after migration.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.