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 manages API-driven integrations, such as techspec/adapter scripts, third-party API adapters, and native REST endpoints, independently of one another, with no centralized layer for policy enforcement, traffic control, or observability across them. Administrators must configure and monitor each integration point separately, which limits consistent security controls and visibility into overall API traffic and performance. This enhancement would introduce a native API Gateway or API Management module with a centralized GUI to configure, monitor, and audit API traffic, including policy templates for rate limiting and caching, security controls such as authentication and IP allow/block lists, resilience mechanisms for isolating failed requests, and observability features such as correlation-ID tracing, log viewing, and alerting on error-rate spikes. Customers managing large-scale, multi-source API integrations would benefit from consistent policy enforcement, improved security posture, and faster troubleshooting through unified traffic visibility.
NetBrain does not currently retain the underlying command output within Network Intent results when the intent is executed in bulk or through a scheduled task, even though this output is available when the intent is run interactively on a single device. This enhancement would preserve and expose the command output associated with each device in bulk and scheduled Network Intent executions, consistent with prior product behavior. Retaining this data would allow operations teams to review the exact basis for diagnosis or troubleshooting outcomes after large-scale or unattended runs, rather than only seeing final results without supporting detail.
NetBrain's REST API and Python API currently do not provide a method to programmatically execute the global 'Full Search' function that is available in the web UI, requiring users to submit each search manually through the interface. This enhancement would introduce an API endpoint that accepts full search queries and returns results equivalent to the UI-based search. Customers who need to run large volumes of searches would benefit from the ability to automate this process, reducing manual effort and enabling integration with external workflows.
In Cloud Manager, add Equinix Fabric as a Cloud Type.
NetBrain currently does not provide detailed usage reporting that shows how individual users interact with the platform, including which QApps, Runbooks, DVTs, or features are being used, how many users rely on a given tool, or how frequently specific devices are accessed. The existing Automation Usage overview on the Domain page also lacks clarity, as it does not explain what its figures represent or how they are calculated. This enhancement would introduce detailed usage analytics and reporting covering per-user, per-feature, and per-device activity, including QApp, Runbook, DVT, and automation/diagnosis execution statistics with clearly defined metrics. This capability would help administrators demonstrate platform value to management, identify unused artifacts for cleanup, and compare usage of overlapping functionality against unique capabilities to better guide automation strategy.
NetBrain currently does not provide a reliable plugin-based method to retrieve the complete list of discoverable VPC resource IDs for Google Cloud (GCP), which limits the accuracy of include/exclude VPC discovery scoping in GCP environments. This enhancement would introduce a GCP-specific mechanism to fetch and validate discoverable VPC resource IDs, aligning GCP discovery capabilities with those already available for AWS and Azure. Customers managing GCP infrastructure would benefit from more accurate and dependable control over which VPCs are included or excluded during discovery, reducing errors caused by incomplete or outdated resource ID lists.
When installing rules through Rule Discovery, users must manually unselect each rule individually if they only want to install a subset, such as vendor-specific rules. This enhancement would add an 'Unselect All' or 'Clear Selection' action to the Config Rule Template selection interface, allowing the full list to be cleared in a single action before filtering and selecting the desired rules. Customers installing targeted rule subsets would benefit from a faster, less error-prone selection workflow.
NetBrain currently requires each Golden Intent to be scheduled individually, with no option to configure scheduling across multiple intents at once. This enhancement would allow users to select multiple Golden Intents and apply or update scheduling settings simultaneously in a single action. Customers managing large numbers of Golden Intents would benefit from reduced administrative effort and faster configuration of recurring checks.
NetBrain currently does not automatically propagate device inventory updates across all nodes in a clustered deployment, requiring administrators to manually verify and synchronize device changes between environments. This enhancement would allow device additions, removals, or updates to be automatically reflected across all cluster nodes without manual intervention. Customers operating multiple synchronized environments would benefit from consistent device visibility and reduced administrative effort in maintaining cluster parity.
NetBrain's webhook follow-up action currently requires users to manually base64 encode their username and password before entering the combined string into the Authorization header when configuring Basic Authentication. This manual step introduces the risk of formatting errors and requires customers to perform the encoding outside of NetBrain using external tools. This enhancement would allow NetBrain to accept a plain username and password for Basic Authentication and automatically perform the base64 encoding internally before constructing the Authorization header. Customers with security requirements around credential handling would benefit from a more streamlined and less error-prone configuration process when setting up webhook integrations.
NetBrain currently enforces a fixed CLI timeout of 5 minutes in Device Settings, which causes long-running commands, such as 'show tech-support' on certain platforms, to fail before completion. This enhancement would allow administrators to configure or extend the CLI timeout value for command execution beyond the current default, independent of other module-specific timeout controls. Customers running commands that require extended execution windows would benefit from reduced task failures and more reliable diagnostic data collection.
NetBrain Runbooks currently do not provide a way to duplicate an existing node within a Runbook, including its full configuration such as CLI commands, golden config rules, intent settings with task variables, or configlet parsers. Users must manually recreate a node and re-enter all settings when a similar validation step is needed elsewhere in the same Runbook, such as when building pre- and post-change comparison steps. This enhancement would add a 'Duplicate Node' option within the Runbook editor, allowing a node and its configuration to be copied to a new node with minimal manual re-entry. Customers performing change validation workflows would save setup time and reduce configuration errors when replicating complex node settings across pre- and post-change steps.
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.
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'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 does not provide a way to copy or duplicate an existing Diagnosis definition, requiring users to manually recreate similar diagnoses from scratch even when only minor changes are needed. This enhancement would add a copy or clone option at the Diagnosis level, allowing users to create a new Diagnosis based on an existing one and then adjust only the necessary details. Customers managing multiple similar diagnoses would save significant configuration time and reduce the risk of manual entry errors when building related Diagnosis definitions.
NetBrain currently requires a default value to be specified for a macro variable used in an auto-intent; leaving the default blank causes the associated command to fail decoding, since the command becomes invalid without a value in place. This enhancement would allow a macro variable's default value to remain empty while preserving valid decode logic, so the command does not error out when no default is supplied. Supporting this would let customers force users to manually enter required input on every execution, improving accuracy and control over auto-intent runs without sacrificing decode reliability.
NetBrain currently limits the time range configurable in scheduled QApp settings to 1440 minutes (24 hours), which prevents customers from defining a monthly scheduling window directly within the QApp settings interface. This enhancement would extend the available time range option to support up to 24*30 hours, allowing a monthly benchmark schedule to be configured natively. Supporting this broader range would remove the need for manual workarounds and give customers greater flexibility when planning longer-interval automated QApp executions.
Network Intent checks currently do not support validating whether a given input value, such as a VLAN ID, falls within an allowed list that combines individual values and ranges (for example, 1-5,7,9-12,13,28,128). Users must rely on manual or basic comparison operators that cannot express range-based membership. This enhancement would add a check type that accepts a mixed list of discrete values and ranges, and evaluates whether the input value is present within that defined set. Customers performing compliance or configuration validation would be able to define allowed value sets efficiently and receive accurate pass/fail results without building complex workarounds.
Hi all,is there a mechanism to redistribute devices evenly among front servers or do I have to do it manually using Shared Device Settings and Device Groups? I have a new FS added to my farm and find myself doing the redistribution manually, trying to find a filter in Device Groups that makes sense.If there is a mechanism, please share. If not, please accept this as an idea.
Use case:I am creating golden config rule to see if last resort password is configured in configuration. As the password is encrypted I am not comparing entire config line. As the password is different per location I am using Golden Base Parameter.example:username lastort1username lastort2 Now, I want to create network intent where I want to build entire config.example:Return from Golden config check is, that “lastort1” is configured, but lastort2 not.I want to check if username from golden base parameter is included in “Unused_patternt_lines” and create entire command including username and password. Username and password should be from golden parameter. Could you please add option to access from network intent to golden base parameter so I can use it for this use case?Case: 00179517
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.