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.
Service Monitor currently raises alerts whenever a monitored service is found stopped, even when the service is intentionally offline, such as a standby node in a multi-datacenter deployment. There is no mechanism to mark a service as expected to be in a stopped state so that Service Monitor can suppress alerts for it. This enhancement would allow administrators to designate specific services or devices as intentionally stopped or in standby mode, so that Service Monitor excludes them from triggering alerts while still tracking their status. This would reduce alert noise and prevent unnecessary escalation for customers running high-availability or multi-datacenter architectures where certain services are expected to remain inactive until failover occurs.
NetBrain currently requires users to move device groups into folders one at a time, selecting each group individually from a dropdown menu and choosing a destination folder. Drag-and-drop and multi-select move actions are not supported, which makes reorganizing a large number of device groups into folders a slow, repetitive task. This enhancement proposes adding multi-select capability to the device group list, allowing users to select several device groups at once and move them together to a chosen folder in a single action. This would significantly reduce the time and effort needed for customers managing large numbers of device groups, particularly when reorganizing an environment after adopting a new folder structure.
NetBrain currently does not provide a way to automatically purge or bulk delete triggered maps once they exceed a defined age, requiring users to remove outdated maps manually one at a time. This enhancement would introduce a configurable retention policy or bulk delete option that allows administrators to automatically remove triggered maps older than a specified number of days. Customers generating large volumes of triggered maps through integrations would benefit from reduced manual maintenance and better control over map repository growth.
NetBrain does not currently provide a direct method to identify all switches, trunk links, and access ports associated with a specific VLAN ID and automatically render that information as an L2 topology map. Customers must rely on manual command output review or ad hoc device grouping to approximate this view, which becomes impractical when many VLANs span multiple VRFs and does not reliably capture access port connections. This enhancement would add a capability to specify a VLAN ID and automatically generate an L2 topology map showing all associated switches, trunk interfaces, and access ports. This would give customers an efficient, accurate way to visualize VLAN-scoped L2 topology without manual workarounds, improving troubleshooting and network documentation for environments with a large number of VLANs.
NetBrain currently does not support discovery and mapping of AWS Gateway Load Balancer (GWLB) resources within cloud environments. This enhancement would add native support for GWLB, allowing the platform to discover, model, and represent GWLB endpoints and associated traffic flows in topology maps. Customers deploying GWLB as part of their AWS network architecture would gain complete visibility into their environment without manual workarounds.
NetBrain path trace currently does not allow a VPN-terminating device to be selected as the first-hop gateway when calculating the path for a VPN client, even when that device is the actual point of entry into the network. In environments where multiple gateway-capable devices exist, the path engine may default to an unrelated device, producing an inaccurate path that does not reflect real traffic flow. This enhancement would allow the path trace engine to correctly identify and offer the actual VPN-terminating device as a selectable gateway option for VPN client path calculations, ensuring the resulting path reflects the true routing behavior. Customers relying on path trace for VPN troubleshooting would gain accurate, end-to-end visibility without needing to manually correct or reinterpret an incorrect calculated path.
NetBrain currently does not reliably complete Path node execution when it is included as part of a scheduled network change task, causing the live post-change path to fail to generate. In addition, when both pre-change and post-change paths are captured, the resulting report does not clearly separate or distinguish the two paths from one another. This enhancement would ensure that Path nodes execute consistently within scheduled change workflows and would present the pre-change and post-change path results as distinct, clearly labeled sections in the generated report. Reliable path execution and clear before-and-after comparison would give customers confidence in validating the network impact of scheduled changes without manual follow-up.
NetBrain does not currently provide an adapter for onboarding Cisco Telemetry Broker (CTB) devices via API, which limits visibility into environments that rely on this platform for telemetry management. This enhancement proposes adding a dedicated CTB adapter, along with documentation of the vendor API details required for integration. Supporting CTB would allow customers to fully onboard and manage these devices within NetBrain, extending discovery and monitoring coverage to telemetry broker infrastructure.
NetBrain currently requires each user to manually select the 'Execute Changes in Bulk' option each time a change template is created, with no way to set this behavior as a default across the organization. This enhancement would introduce an administrator-configurable global setting that allows the 'Execute Changes in Bulk' option, and potentially other change-execution behaviors, to be set as the default for all users. Administrators would define the setting once, rather than relying on each user to configure it individually. This reduces repetitive manual configuration, ensures consistent change-execution behavior across teams, and lowers the risk of inconsistent settings when multiple users create templates independently.
NetBrain does not currently provide a validated or natively supported adapter for integrating with Arista DANZ monitoring fabric devices, requiring customers to build and maintain their own custom adapters. This enhancement would add native support for Arista DANZ within the Integrated Edition, including a certified adapter that can be verified and maintained by the product team. Customers operating Arista DANZ environments would benefit from consistent, supported integration rather than relying on unverified custom-built adapters, reducing maintenance overhead and improving reliability of network visibility data.
Golden Configuration parsing currently treats JSON-formatted content as plain text, so start and end line markers break the JSON structure and prevent it from being recognized as valid JSON. As a result, parent and dependency options available for other configuration patterns cannot be applied to JSON blocks, and complex scenarios involving multiple JSON fragments or variables produce a flattened table instead of a single reconstructed JSON object, forcing instance-based checks where a single key/value check would suffice. This enhancement would extend the parsing engine to recognize and preserve JSON formatting, allowing parent and dependency options to apply to JSON patterns, and would add the ability to reconstruct or reassemble parsed JSON fragments into a single cohesive structure when building the golden configuration. Supporting native JSON parsing would let customers isolate and validate specific configuration segments, such as edge-specific portions separate from profile-level configuration, while relying on straightforward key/value based checks rather than complex instance-based workarounds.
NetBrain currently defaults the login screen to the local NetBrain authentication method, requiring users to manually switch to SSO each time they log in, even in environments where every user authenticates exclusively through SSO. This enhancement would allow administrators to configure SSO as the default authentication method presented on the login screen. Customers operating in SSO-only environments would benefit from a streamlined login experience, reducing unnecessary manual steps for every user session.
NetBrain currently does not provide a way to duplicate a map under a new name while preserving the runbook's per-device command associations. When a map is saved as a new map, the runbook and its results are lost, and when a runbook is saved as a template, the per-device command scoping is not preserved, causing all commands to be applied to every device instead of only the intended ones. This enhancement would allow a map to be duplicated or renamed with its runbook intact, retaining the specific command-to-device associations exactly as configured in the original map. Customers who repeatedly execute similar changes across the same set of devices would save considerable time by reusing a proven runbook configuration instead of manually re-entering device-specific commands for each new change reference.
NetBrain path trace currently does not support multicast path calculation on Juniper routers, limiting visibility during multicast troubleshooting scenarios. This enhancement would extend the path trace engine to recognize and correctly compute multicast paths across Juniper devices. Customers troubleshooting multicast traffic in mixed-vendor environments would gain complete, accurate path visibility without needing manual workarounds.
When configuring a Runbook input dialog with device scope set to an ADT or Device Group, the dropdown list is limited to approximately 500 entries and offers no search or filter function, making it difficult to select from within larger groups. This enhancement would raise the dropdown display limit and add a search field so that specific devices can be located and selected without scrolling through the full list. Customers managing device groups in the thousands would gain a practical way to configure Runbook inputs accurately and efficiently.
NetBrain currently requires users to remove entries from the Devices to Be Discovered list one at a time, which is inefficient when managing large discovery queues. This enhancement would add a Delete All Entries option to clear the entire list in a single action. Customers managing large-scale discovery operations would benefit from reduced manual effort and faster list maintenance.
I noticed, that in NetBrain we have build in API for FortiManager. I tried to add our FortiGate manager there, but I found out, that it's not supporting discovery of firewalls. Could you please consider adding support for firewall discovery using existing FortiManager API?Case: 00180683
In Multi-Vendor Support, Vendor Model, when you add a new SysObjectID, please sort the list of vendors alphabetically without differentiating between upper case and lower case letters. In this list, APC comes before Acgate and CXR Telecom comes before Cisco.Capital letters (upper case) are generally considered to be identical to their corresponding lower case letters for the purposes of alphabetical ordering, as in this case.I also found the vendors Allen-Bradely and Allen-Bradley in this list, surely one of them is a typo.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.