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 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.
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.
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.
NetBrain currently selects representative devices for test replication without regard to whether those devices are fully accessible, which can include devices with only partial connectivity such as SNMP-only or ping-only access. This limits confidence in replication outcomes, since a failure or inconsistency may stem from incomplete device access rather than the model or intent being tested. This enhancement would allow the representative device selection process for test replication to consider only devices that are fully accessible to NetBrain, such as those with confirmed CLI or API access. Customers would gain greater confidence that replication results reflect the actual behavior of the network intent rather than being skewed by device access limitations, reducing troubleshooting effort and improving the reliability of automation testing.
NetBrain currently does not automatically populate MPLS cloud objects on a map when a device is dragged and dropped onto that map. Users must take additional manual steps to have the MPLS cloud object appear and connect correctly with the newly placed device. This enhancement would ensure that MPLS cloud objects are automatically detected and rendered on the map as part of the drag-and-drop workflow. Customers building or maintaining WAN topology maps would benefit from more accurate, complete topology visibility without extra manual configuration steps.
Universal Dashboards currently cannot be exported to Word or any other document format, and they are not available as a selectable content type within the Content Template Manager. This enhancement proposes adding native export functionality for Universal Dashboards to Word, along with an option to include Universal Dashboards as a component when building new Word document templates through the Content Template Manager. Supporting these capabilities would streamline the documentation workflow for partners and end users, allowing dashboard insights to be incorporated directly into reports and templates without manual recreation.
Chatbot macros currently require input values to be fed through a single, uniform method across all macros in a bot, with no option to assign a different input source per individual macro. This enhancement would allow each macro within a chatbot to be independently configured with its own input source, such as manual entry for one macro and an external table feed (for example, an ADT-backed source) for another. Customers building chatbots that reference a mix of static and dynamically sourced values, such as IP, MAC, and location data, would be able to configure each macro according to how that data is actually maintained, reducing manual upkeep and improving the accuracy of automated responses.
Plugin Manager currently does not provide a shared folder option, which limits users to organizing plugins in personal or local locations only. This enhancement would introduce a shared folder within Plugin Manager, allowing multiple users to access, organize, and manage a common set of plugins in one place. Customers with distributed teams would benefit from improved plugin reuse and consistency, reducing duplicate effort and simplifying plugin governance across the organization.
Portal users interacting with the Chatbot currently have no way to create or calculate a network path directly within the conversational interface. This enhancement would allow users to specify source, destination, and port inputs through the Chatbot to trigger path creation and to view or live-calculate the resulting path and associated applications. Extending path capabilities into the Chatbot would give customers a faster, more accessible way to perform path troubleshooting without switching to the full application interface.
When a change is created through the Remediation action within a Network Intent, the system does not use a map object that the user has already created and saved; instead, it relies on a different, unsaved map for change creation. This requires the user to separately save the map used during the change process, creating an inconsistent workflow. This enhancement would allow users to specify which existing map object should be used for change creation when a Remediation action is triggered from a Network Intent. Supporting this capability would reduce redundant map-saving steps and provide consistent, predictable behavior when generating changes from automated diagnostics.
When using an Automated Data Table as the source for candidate devices in Chat Bot, the dropdown menu currently displays all devices in the table regardless of whether each device has the relevant replicated Network Intent data. This means devices without the applicable replicated data still appear as selectable options, requiring manual verification before use. This enhancement would add a filter to the Chat Bot candidate device dropdown so that only devices with the required replicated Network Intent are shown. Customers using ADT-driven Chat Bot workflows would gain a more accurate device selection experience and reduce the risk of choosing devices that lack the necessary data for the intended automation task.
NetBrain currently renders the Bus icon on L2 and L3 maps using a fixed, non-configurable appearance, giving administrators no way to visually distinguish or customize how shared network segments are represented. This enhancement would allow administrators to select or configure an alternative icon for the Bus element on maps. Providing this flexibility would improve map readability and let customers align the visual representation of shared segments with their own diagramming conventions.
NetBrain currently rebuilds Automated Data Tables (ADTs) on every scheduled or triggered cycle, regardless of whether the underlying seed intent has actually changed, which consumes unnecessary processing time and system resources. This enhancement would introduce a change-detection mechanism that compares the current seed intent state against the prior state and initiates a full ADT rebuild only when a meaningful change is detected. This capability would reduce processing overhead and shorten rebuild cycles, particularly benefiting environments with large device inventories or frequent scheduled rebuild intervals.
NetBrain does not currently update a Path Browser task's status to Failed when the task process is terminated externally, such as through a system task manager. As a result, the task status may remain inaccurate or unclear, leaving no reliable indicator that the task did not complete successfully. This enhancement would detect external termination of a running Path Browser task and update its status to Failed accordingly. Accurate status reporting would give customers confidence in monitoring task outcomes and would reduce the need for manual verification when a task is unexpectedly stopped.
NetBrain currently does not allow users to filter neighbor devices by device type when a map is generated through an API-triggered diagnosis; all discovered neighbors are added to the map regardless of type. This enhancement would introduce a filtering option that lets users specify which device types to include or exclude from neighbor discovery during API-driven map creation. Customers running automated diagnostic workflows would be able to generate more focused and relevant maps, reducing manual cleanup and improving the efficiency of automated troubleshooting.
In the Runbook Compare feature, the 'Default Live' option is labeled in a way that suggests it will retrieve current live data, but it actually pulls only from data already present in the table and returns no results unless a separate retrieve action has been run first. This naming creates confusion, as users expect 'Default Live' to behave similarly to the 'Retrieve Data' action. This enhancement would rename the option to more accurately reflect its behavior, such as 'Temporary Data,' or remove it from contexts where it does not provide value. Clarifying this option would reduce user confusion and prevent customers from misinterpreting comparison results as reflecting live device data when they do not.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.