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 shows an icon in the Neighbors window only when a neighbor device is both on the map and linked, with no way to distinguish neighbors that are already on the map but not yet linked. This enhancement would add a distinct indicator for neighbors that are present on the map but lack a link, alongside the existing on-map-and-linked icon. Customers building maps through Auto Link or manual expansion of the Neighbors window would be able to quickly identify which on-map devices still require linking, reducing the manual effort needed to complete topology connections.
NetBrain currently does not allow a saved SNMP credential name to be edited; changing the name requires creating an entirely new credential entry, which leaves the original in place and can lead to duplicate or unused credential records over time. This enhancement would allow the name field of a saved SNMP credential to be edited directly without requiring a new credential to be created. Customers managing credential naming conventions or correcting entry errors would benefit from a simpler maintenance process and a cleaner credential list.
NetBrain currently allows a GApp to select 'Current Baseline' as a data source option even when that option is not enabled on any of the QApps used to build the GApp, and there is no visible setting to configure or restrict the data source at the GApp level. This can lead to unexpected results when the GApp runs against a data source it was not actually configured to support. This enhancement would validate the GApp data source selection against the data source settings enabled on its constituent QApps, either by restricting selectable options to those supported or by surfacing a clear configuration control and warning when a mismatch exists. Preventing this inconsistency would help customers avoid unexpected or inaccurate automation results and reduce troubleshooting time when diagnosing GApp output discrepancies.
NetBrain's OneIP Table export currently produces a full data set without an option to limit results to IP addresses associated with a specific group of devices, such as a Device Group. Users who need IP data for only a subset of their environment must export the complete table and manually filter it afterward. This enhancement would add the ability to select a Device Group as a filter criterion prior to export, so that only IP addresses related to devices in that group are included in the output. Customers managing large or segmented environments would benefit from reduced manual post-processing and more efficient access to relevant IP data for audits, troubleshooting, or reporting.
The Observability dashboard currently sorts device groups only by alert count, from highest to lowest, with no option for users to define a custom display order. This enhancement would allow administrators to manually arrange device groups within the dashboard, such as by an assigned priority tier, rather than relying solely on alert volume. Customers who organize their network by business-defined priority levels would gain a dashboard view that reflects their operational priorities, improving triage efficiency and alignment with internal service tiers.
When an alert is raised for a device where a specific monitored instance is not configured, the resulting alert does not include the instance information, and the alert message does not clearly communicate that the instance is missing. This makes it difficult for users to understand the root cause of the alert without additional investigation. This enhancement would ensure the instance details are included in the alert output and would update the alert message text to explicitly state when a configured instance cannot be found on the device. Providing this context would help customers quickly understand what is missing and reduce the time spent troubleshooting alert conditions.
Today, when a user selects a date range or a preset window such as the last 7 days for the Change Analysis Report, the report only compares consecutive configuration files rather than showing the net difference between the range's starting and ending dates. This limits visibility into the overall change footprint across a selected period, since users must manually review each incremental comparison to reconstruct the full picture. This enhancement would add the ability to generate a Change Analysis Report that compares the configuration at the start of a selected range directly against the configuration at the end of that range, in addition to the existing consecutive-file comparison. Providing this option would help customers quickly identify the cumulative changes over a time period without manually reviewing every intermediate comparison, improving efficiency for audit and troubleshooting workflows.
The functional portal today relies on static collateral and predefined content to answer internal user questions, which requires ongoing maintenance and often fails to surface the specific answer a user needs. This enhancement would introduce a natural language AI assistant within the functional portal, allowing users to ask questions directly and receive relevant answers drawn from portal content and underlying network data. This capability would reduce the burden of maintaining static documentation and improve the perceived value of self-service by helping internal users find answers more efficiently.
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.
Dashboards and Summary Dashboards currently display alert conditions for devices but do not provide a way to visualize those alerting devices together on a map. Users must manually locate and add each alerting device to a map to review its position and context within the network. This enhancement would add an option to open a new map automatically populated with all devices currently showing alerts on a dashboard widget. Customers would gain faster visibility into the scope and location of active alerts, reducing the manual effort needed to investigate and respond to network issues.
NetBrain currently displays QApp input parameters of type password as clear text within the QApp execution log, exposing sensitive credential values to anyone with log access. This enhancement proposes masking password-type input values in the execution log output, consistent with how such values are handled in other parts of the interface. Masking these values would reduce the risk of credential exposure and help customers meet security and compliance requirements around sensitive data handling.
NetBrain currently does not provide a function or ADT option that returns whether a device connection was established using SSH or Telnet. As a result, automation and remediation scripts cannot conditionally verify the login protocol before taking action on a device. This enhancement would introduce a callable function or ADT option that returns the protocol used for the current device session. Customers enforcing security policies that require disabling Telnet only on devices confirmed to use SSH would be able to automate this validation safely, reducing the risk of losing connectivity to devices where SSH is not functioning.
QApp input dialogs currently support only static, pre-defined dropdown lists for parameter selection, with no mechanism to refresh the available options from an external data source before the QApp runs. This enhancement would allow a QApp input to call an API at runtime to retrieve a current set of selectable values, populate the dropdown with those items, and let the user choose one before execution. Customers whose valid input values change frequently would be able to select accurate, up-to-date options without manually editing the QApp definition each time the underlying list changes, reducing maintenance effort and the risk of running a QApp against stale input values.
The QApp input window currently displays with a fixed width that cannot be adjusted by the user, which can make it difficult to view or enter longer input values comfortably. This enhancement would allow users to manually resize the width of the QApp input window to fit their content. Providing this flexibility would improve usability for customers who work with QApps requiring longer input strings or multiple input fields.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.