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.
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.
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.
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.
NetBrain currently requires users to input AWS access key and secret key values for API accounts during initial onboarding, but provides no supported way to update these credentials afterward when a customer rotates or changes the keys; administrators must resort to direct database updates to apply the new values. This enhancement would add a UI-based option to update the user ID and access/secret key pair for existing AWS API accounts configured under the combined access method, without requiring backend intervention. Customers who follow periodic key rotation practices for security compliance would benefit from a supported, self-service way to keep AWS API credentials current and avoid dependency on manual database changes.
Self-Service activation for triggers is currently limited to triggers that are directly associated with an Incident Type, so triggers configured outside that association cannot be enabled for Self-Service use through the Incident or Incident Portal. In addition, all Self-Service enabled triggers appear within an incident without any filtering, regardless of whether they apply to devices present on the incident map. This enhancement proposes adding a separate control within the Triggered Diagnosis Center that allows Self-Service to be activated for NI or NIC triggers independent of their Incident Type association. It also proposes a filtering mechanism so that only Self-Service triggers applicable to the devices on the incident map are displayed. Together, these changes would improve usability by broadening where Self-Service can be applied and by reducing irrelevant trigger clutter within an incident.
NetBrain currently supports email notifications only for errors or alerts, but does not provide a way to email the actual results of a completed Runbook execution. This enhancement would add an option to automatically send Runbook execution results via email once a run completes, giving operations teams direct visibility into outcomes without needing to log in and navigate to the results manually. This capability would improve operational efficiency for teams that rely on timely review of Runbook outputs.
When exporting a map to Word, the generated document currently includes Asset Data content in addition to the accompanying Excel file, with no option to omit it. This enhancement proposes adding a configurable option to exclude Asset Data from the Word output while still producing the associated Excel file. Customers who only require the Excel data would benefit from a cleaner export process and would no longer need to manually remove unwanted content from the Word document.
Site maps currently use a standardized naming suffix for certain map types, such as '_L2' for Layer 2 maps and '_Nbr' for Neighbor maps, but the L3 map for a site does not receive a corresponding distinguishing suffix. This enhancement would add a consistent '_L3' suffix to L3 site maps, aligning the naming convention across all map types generated for a site. Providing this consistency would help customers quickly identify map types when navigating between multiple site maps, reducing confusion and improving overall usability.
NetBrain currently requires administrators to log into the worker server directly to manually enable debug-level log output for discovery operations, which is inconvenient for both customers and support teams during troubleshooting. This enhancement proposes adding a control within the web front end that allows authorized users to enable or disable discovery debug logging without server-side access. Providing this capability from the UI would streamline troubleshooting workflows and reduce the time required to diagnose discovery issues.
NetBrain does not currently provide a report that displays the execution time of configuration retrieval across devices over time. Administrators in environments with intermittent retrieval failures have no efficient way to identify which devices have experienced retrieval issues repeatedly or over an extended period. This enhancement would add a report showing configuration retrieval execution time by device, allowing administrators to quickly spot devices with recurring or long-standing retrieval problems. Customers managing large or unstable environments would benefit from faster identification of problematic devices and reduced manual investigation effort.
NetBrain's Retrieve Live Data process can display a success (green) icon even when the underlying configuration update fails because a hostname change was detected on the device during the update, giving users a false indication that the update completed successfully. This enhancement would update the status icon logic to reflect a failure state whenever a detected hostname change prevents the configuration update from completing, rather than reporting it as successful. Accurate status reporting would help customers trust the retrieval results and avoid overlooking real configuration update failures during troubleshooting or automated runbook execution.
NetBrain's search function currently cannot locate a device by hostname when that hostname encodes a MAC address using a vendor naming convention, such as Cisco VoIP phone hostnames. The search also does not query CDP/NDP neighbor table data, so devices that are visible only as neighbors of managed switches cannot be found by hostname even though the network already reports the hostname-to-MAC relationship. This enhancement would extend search to normalize and correlate hostname patterns that embed a MAC address against the corresponding MAC record, and would allow search to include CDP/NDP neighbor table entries as a searchable data source. Customers working with unmanaged neighbor devices, such as VoIP phones, would be able to locate them directly by hostname without manually reformatting the search term, reducing repetitive effort during troubleshooting.
The built-in Interface Inventory Report currently supports only a fixed set of predefined columns and does not allow values derived from custom plugins to be displayed alongside standard interface attributes. This enhancement would allow users to add a custom column to the Interface Inventory Report that displays a value set through a plugin, enabling plugin-derived data to appear in the same table as native interface fields. Customers who rely on plugins to compute or assign custom attributes would benefit from a unified report view that consolidates both standard and customized data without needing separate tools or manual cross-referencing.
NetBrain currently allows administrators to export and import device lists, credentials, sites, and AAM configurations between domains, but does not support export and import of API stubs, intents, guidebooks, or probes. This limits the ability to fully replicate a domain's configuration when standing up a new environment. This enhancement would extend the existing export/import functionality to include the database collections for API stubs, intents, guidebooks, and probes, alongside the currently supported items. Customers setting up new domains, such as for proof-of-concept or new customer onboarding, would benefit from a complete and consistent way to clone domain configurations without manually recreating these components.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.