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 Webhook API follow-up action currently supports opening a ServiceNow Incident from a Network Intent diagnosis, but it does not support opening a ServiceNow Change Request through the same mechanism, nor does it provide a way to link that Change Request to a Change Management task within NetBrain. This enhancement would extend the Webhook API follow-up action to support Change Request creation in ServiceNow and would allow the resulting Change Request to be linked to a corresponding CM task or runbook in NetBrain. Customers would benefit from an automated workflow in which a diagnosis-triggered change process is initiated and tracked consistently across both platforms, reducing manual coordination between diagnosis and change management activities.
NetBrain currently provides no in-product explanation for why Intent Diagnosis results may fail to save during Proactive Automation (PA) executions, leaving customers without context when this scenario occurs. This enhancement would add guidance to the Help Icon describing the common causes of Intent Diagnosis results not saving during PA executions. Surfacing this information would help customers self-diagnose the scenario and reduce reliance on support engagement for clarification.
NetBrain currently sorts file and folder names using standard alphanumeric string comparison, which can produce an order that does not match human expectations when names contain numbers, such as placing 'File10' before 'File2'. This enhancement would apply a natural sort algorithm to file and folder listings so that numeric segments within names are compared by value rather than by character. Customers managing large numbers of files and folders would benefit from a more intuitive, human-readable ordering, reducing the need for manual workarounds such as zero-padding names to force correct sort order.
Service Monitor and the Server Health Report currently do not display the time reported by each monitored server, which makes it difficult for administrators to identify time synchronization issues between servers. This enhancement would add a column showing each server's reported time, including time zone information or a UTC-converted value, within both the Service Monitor interface and the Server Health Report. Providing this visibility would help administrators quickly detect and troubleshoot server time mismatches, reducing the effort required to diagnose issues that stem from clock discrepancies.
When configuring Trigger Automation, administrators currently have no way to see the folder path or source location of the Network Intent being used, making it difficult to determine whether the Intent is a standalone NIT or one associated with IBAC, and from which folder it originates. This enhancement would display the full path or source location of the selected Intent directly within the Trigger Automation configuration screen. Providing this visibility would help engineers, particularly those new to an environment, quickly identify and verify the correct Intent without manually searching through folders.
Benchmark tasks currently support only CLI-based commands for collecting device data used in Datasets, leaving no option to gather data via SNMP. This enhancement would add support for configuring SNMP-related commands within a Benchmark task so that SNMP responses can be captured and used as Dataset input alongside CLI-based data. Customers working with devices where SNMP is the preferred or only available access method would gain the ability to decode and populate Datasets without relying solely on CLI connectivity, improving flexibility and completeness of Benchmark-driven data collection.
NetBrain's REST API currently does not provide a documented method for retrieving the result data of QApp-based reports, such as Inventory Reports, leaving customers unable to programmatically access this output outside of manual export or UI review. This enhancement would introduce a documented API endpoint that allows customers to retrieve QApp and Inventory Report results directly through the API. Customers building automated reporting or monitoring workflows would benefit from consistent, programmatic access to report data without relying on manual retrieval steps.
In multi-tenant environments, users who are granted the User Management privilege can currently view Applicant List, Existing User List, and Edit User details for all tenants and domains on the platform, rather than only their own. This enhancement would scope the User Management privilege so that a user with this privilege can view and manage only the applicant and user account information belonging to their assigned tenant or domain. This capability would be particularly valuable for MSP deployments, where multiple customers share the same platform and administrators must be prevented from viewing user information belonging to other tenants.
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.
When using a CSV within Network Intent, a static value referenced by the CSV currently must be entered separately in each diagnosis that uses that CSV, with no mechanism to define it once and have it apply universally. This enhancement proposes allowing a static value to be configured a single time for a given CSV and automatically reflected wherever that same CSV is referenced across diagnoses. Customers managing multiple diagnoses built on shared CSV data would benefit from reduced manual configuration effort and lower risk of inconsistent values across related intents.
NetBrain's Tune Live Access tool currently reports only a succeeded or failed connection status for each device, without indicating whether SSH or Telnet was used, so administrators must inspect individual device logs to determine the protocol. In addition, testing a specific protocol requires manually changing the default VTY or access mode setting for each device before running the tool. This enhancement would add an option to select and force a specific protocol, such as SSH-only or Telnet-only, when running Tune Live Access, along with a dedicated column in the results table that shows the protocol used per device. Customers would be able to validate protocol-specific reachability and quickly identify which devices use SSH versus Telnet directly from the exportable table, removing the need to review logs on a per-device basis.
NetBrain currently labels the option that refreshes the device selection on a Runbook node as 'Reload Target Devices.' This wording can be misread as an action that power-cycles or reloads the physical devices themselves, causing unnecessary concern among users who are cautious about NetBrain's read-only access model. This enhancement would rename the option to more accurately describe its function, such as 'Refresh Target Devices' or 'Refresh Device Selection.' A clearer label would reduce customer confusion and reinforce confidence that the action only updates device selection data on the map rather than affecting live network devices.
Network Intent currently supports Ping and Traceroute checks executed from the Front Server, but it does not provide an option to perform an SNMP walk from the Front Server to verify device reachability via SNMP. This enhancement would add an SNMP walk execution option within Network Intent, consistent with the existing Front Server-based Ping and Traceroute options. Customers troubleshooting device-down or node-down alerts would gain a more complete reachability assessment, reducing manual verification steps and improving the accuracy of automated network health checks.
NetBrain currently requires users to manually upload five separate icon image files to represent the different status color states for a single device type in the Change Device Type Icon window. This enhancement would introduce backend logic to automatically generate the required color variants from a single uploaded base icon. Automating this process would reduce manual effort for customers managing custom device icons and ensure visual consistency across status states.
Summary Dashboards currently display an overall trend indicator but do not show which specific devices or checks contributed to an improvement or degradation between runs. Users monitoring a continuously running or periodically scheduled dashboard have no way to identify what changed since the previous run without manual comparison. This enhancement would add a detail view or drill-down that highlights the specific devices and checks whose status changed between the current and prior run. Customers relying on frequently refreshed dashboards would gain faster insight into emerging issues and improvements, reducing the manual effort needed to interpret trend changes.
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 does not provide a way to transfer or release editing rights for Summary Dashboards, nor does it offer an option to lock a dashboard to prevent unauthorized changes. This enhancement would add the ability for administrators to assign or revoke editing rights to specific users or groups, and to lock a dashboard to restrict edits until explicitly unlocked. This capability would allow users beyond the administrator to safely manage dashboard content, improving collaboration while protecting dashboards from unintended modification.
NetBrain currently does not provide a way for administrators to designate which data collection method, CLI or API, should serve as the authoritative source when both are configured for a device. When the two sources report conflicting values for items such as configuration content, serial number, or interface status, the platform has no defined precedence rule, which can lead to inconsistent or inaccurate data being displayed or used in downstream tasks. This enhancement would add a global setting that lets administrators specify a primary data source, either CLI or API, with the secondary source used automatically only when the primary source is unavailable or fails to return data. Customers operating hybrid environments with both CLI and API-managed devices would gain more predictable data accuracy and reduced troubleshooting effort tied to source conflicts.
NetBrain currently serves the desktop web interface and the administrator web interface on the same port, which does not allow administrators to isolate or restrict access to the administrative console independently of the standard user interface. This enhancement would allow administrators to configure desktop.html and admin.html to be accessible through separate, independently configurable ports. Customers would benefit from improved network segmentation and security control, allowing administrative access to be restricted to specific network segments or firewall rules without affecting general user access to the desktop interface.
NetBrain currently restricts the IsL2Border and IsL3Border configuration options within DVT to logical node device types, leaving these options unavailable when a traditional device is selected. This enhancement would extend the availability of the IsL2Border and IsL3Border options to traditional devices, aligning their configuration capability with logical nodes. Providing consistent access to these border designation options across both device types would support more accurate and flexible topology modeling in DVT-based workflows.
Intent Dashboards and Summary Dashboards currently cannot be exported as a formatted, chart-inclusive document such as PDF; available export paths do not preserve the visual summarization and graphics shown on screen. This enhancement would add a native PDF export option for these dashboards that retains charts, graphics, and layout as displayed in the product. Customers and partners preparing executive-level or management-facing reports would benefit from being able to share polished, presentation-ready dashboard output with stakeholders who do not have direct access to NetBrain.
The Domain Health Report currently displays a CLI Privilege Login status indicator for all devices, even in environments where privileged CLI login is not used because access control is managed entirely through an external AAA system. This results in a persistent 'N/A' alarm that cannot be dismissed or excluded from the report. This enhancement would allow administrators to disable the CLI Privilege Login check within the Health Report for domains or device groups where it does not apply. Providing this control would reduce non-actionable alerts and help administrators focus on health metrics that are relevant to their actual access control configuration.
NetBrain Network Intent can generate a compliant configuration based on a golden template, but it cannot push that generated configuration to the target device directly; completing the deployment currently depends on an external system or process outside of Network Intent. This enhancement would allow Network Intent to execute the push of the generated configuration as part of its automated workflow, while still respecting existing change management controls. Enabling this capability would let customers complete configuration remediation end-to-end within NetBrain, reducing reliance on external tools and streamlining automated change workflows.
Today, the chatbot IF condition can only direct next steps based on the results returned by a previous intent, with no option to define the branching manually. This enhancement would add a manual selection option to the IF condition dropdown, allowing a user to choose a specific value to drive the next step rather than relying solely on intent output. Providing this manual option would give automation designers greater flexibility when building conditional chatbot flows, particularly in cases where the desired branching logic does not depend on intent results.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.