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 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 requires A-B path scheduling through AAM/Benchmark tasks to include all path devices within an existing Benchmark scope. Organizations with multiple Benchmarks already configured for different parts of their network find this setup cumbersome, since new A-B path requirements often do not align cleanly with existing Benchmark boundaries. This enhancement proposes introducing a distinct Path Task type within Domain Management/Schedule Tasks, positioned alongside the existing Benchmark Task and Discovery Task options, that links to AAM without requiring path devices to fall within a single Benchmark scope. This would give administrators a more flexible and organized way to schedule A-B path monitoring, reducing setup complexity for networks with multiple, independently scoped Benchmarks.
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.
When a user changes the source associated with a trigger rule under Incoming Incident configuration, all previously defined rules and customer variables are deleted rather than preserved. This enhancement would allow the source to be changed without removing existing trigger rules and variables, or would prompt users with a clear warning and option to retain or migrate the configuration before any deletion occurs. Preserving this configuration would prevent unintended data loss and reduce the effort required to reconfigure complex trigger setups after a source change.
Chat Bot automation currently executes only one Network Intent at a time, even when multiple intents share a matching tag or are selected together within an Automated Data Table. This enhancement would allow multiple intents to be triggered and run concurrently, either through tag-based matching or by selecting multiple intents within the ADT for simultaneous execution. Enabling concurrent intent execution would allow end users to perform multiple diagnostic checks in a single automation cycle, reducing troubleshooting time and improving overall efficiency of automated workflows.
Service Monitor's log collection currently requires administrators to specify an end time when retrieving server logs, and selecting the latest available time in the GUI can still leave a gap of several minutes, preventing visibility into the most recent log entries. This enhancement would allow administrators to leave the end time field empty so that Service Monitor automatically fetches the latest available log data up to the current moment. Customers troubleshooting active issues would benefit from having immediate access to the most current log information without needing to repeatedly adjust or guess an accurate end time.
NetBrain Smart CLI currently does not display the Share/Publish and Incident options when a user establishes a Direct Connect session to a device, even though these options are available when connecting through saved Connections or New Connection workflows. This enhancement would extend Direct Connect sessions to support the same Share/Publish and Incident creation options available in standard Smart CLI connections. Providing consistent access to these options would allow users to capture and publish command output to an Incident regardless of how the device connection was established, improving workflow consistency during troubleshooting.
NetBrain's path browser does not currently offer a way to select a specific date or timestamp and view the status of all paths as of that time in a single batch action; users must open each path's history individually to determine whether it was working at a given point. This enhancement would add a batch option to select a timestamp and display the corresponding status for all paths in a domain or map at once. Customers troubleshooting widespread path failures, such as after a network or software upgrade, would benefit from quickly identifying which paths changed status without reviewing each one manually.
NetBrain currently offers a limited set of default timer intervals for scheduling Network Intent execution, which does not include options aligned to common compliance review cycles. This enhancement would add additional default timer options, such as weekly, monthly, and quarterly intervals, so that compliance-focused Network Intents can be scheduled without requiring custom timer configuration. Customers running periodic configuration compliance checks would benefit from ready-to-use scheduling options that match standard reporting and audit cycles, reducing setup effort and ensuring consistent execution timing.
NetBrain scheduled Discovery tasks, including 'Discover All Live Network', currently run CLI and API discovery methods together without an option to exclude one or the other. Administrators who need to isolate discovery issues cannot limit a scheduled run to CLI-only discovery without also affecting API-based discovery. This enhancement would add a configuration option within scheduled discovery tasks to disable the API discovery method independently of CLI discovery. Providing this control would allow administrators to isolate and troubleshoot discovery issues more efficiently without impacting the full discovery scope.
NetBrain currently does not provide a way to embed custom company or partner logos directly on site topology maps. This enhancement would allow administrators to upload and place one or more logo images onto a site map, such as a service provider logo alongside a customer logo. Providing this capability would help customers and partners present co-branded network documentation, supporting clearer identification of ownership and improving the professional presentation of shared topology views.
Network Intents currently cannot reference variables or tables that were captured or computed in a parent Network Intent when a child Network Intent is executed. As a result, child intents must independently re-run commands to obtain data already available at the parent level. This enhancement would allow a child Network Intent to access select variables or tables from its parent, similar to how later canvases in a qApp can reference tables generated in earlier canvases. This would reduce redundant command execution, conserve memory in large-scale environments, and simplify troubleshooting of nested Network Intent logic.
NetBrain's Smart CLI login dialog currently provides no visible feedback once a user enters credentials and clicks OK, and the connection status display does not indicate which protocol (SSH or Telnet) is being used to reach the device. When the default protocol is Telnet and the device does not respond, users only see a generic connecting message followed by a timeout, with no indication of the protocol attempted or that the login action was received. This enhancement would add clearer in-progress feedback after credentials are submitted and would display the protocol being used during connection attempts, for example showing distinct status messages for SSH and Telnet targets. Customers would benefit from reduced confusion when troubleshooting failed or delayed Smart CLI connections, since the protocol and connection state would be visible without needing to inspect device settings separately.
NetBrain currently does not indicate which NCT tables are supported by a given device driver, making it difficult for users to determine the correct tables to select when configuring benchmark tasks. This enhancement would add a field or reference view that lists the NCT tables supported by each driver. Customers would benefit from selecting only the necessary tables during benchmark configuration, reducing task time and avoiding path failures caused by missing table data.
Under MSP licensing, Function Module node allocations are currently tied to the Tenant level and apply uniformly across all Domains within that Tenant, rather than being configurable per Domain. This means administrators cannot allocate a higher node count to Domains overall while allocating a smaller, distinct node count specifically for Function Modules, limiting flexible provisioning across Domains. This enhancement would allow administrators with MSP licensing to assign Function Module node counts independently per Domain, separate from the overall Domain node allocation. Customers would benefit from greater licensing flexibility, more efficient use of available node capacity, and an easier path for upselling Function Modules to MSP customers.
When creating or editing tenants in an MSP-enabled licensing configuration, administrators currently cannot see how many Cross-domain Monitoring, Automation, or IT Business Analytics nodes have already been assigned to other tenants versus how many remain available. This enhancement would display the assigned and remaining node counts for each function module directly within the tenant creation and edit screens. Providing this visibility would help administrators allocate node licenses accurately across multiple tenants and avoid over-provisioning or under-provisioning during setup.
NetBrain currently allows the Live Thread Pool setting to be configured only at the individual Tenant or Front Server level, with no option to manage it as a single global setting. In environments with a large number of Tenants and Front Servers, this requires administrators to update the value manually and repeatedly across every instance to prevent SSH credential lockouts during benchmark task execution. This enhancement would introduce a system-level Live Thread Pool setting that administrators can configure once and apply globally across all Tenants and Front Servers. Customers managing large-scale deployments would benefit from reduced administrative overhead and a lower risk of SSH credential lockouts caused by inconsistent thread pool values across the environment.
NetBrain currently does not surface the count or list of devices whose latest CLI configuration retrieval failed on the Start Page or in the Health Report, requiring administrators to navigate into Data Accuracy Resolution to identify them. This enhancement would add this category as a visible metric on the Start Page and within the Health Report. Providing this visibility would allow administrators to quickly identify and act on devices with CLI retrieval failures without manual drill-down, since this is a commonly occurring and easily identifiable device access issue.
NetBrain currently displays the same CLI credential configuration under inconsistent labels across different areas of the product, including the domain management page, the device-level settings, and the Change Management task interface. This inconsistency in terminology can cause confusion for administrators trying to locate or configure the correct setting. This enhancement would standardize the naming of this CLI credential setting across all UI locations where it appears, ensuring a single, consistent label is used throughout the product. Customers would benefit from reduced confusion and a more intuitive administrative experience when managing CLI credentials for change execution.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.