NetBrain Feature Requests
Browse, vote, and track the status of feature requests from the NetBrain community
Open
Browse open ideas available for voting, feedback, and discussion.
On the Roadmap
View ideas that are planned for future product development.
In Development
Explore ideas that are currently being developed by the product team.
Available
Explore ideas that are now available in the product.
Not Planned
View ideas that are not currently planned for product development.
Filter by idea status
Filter by features
1113 Ideas
Native path calculation for device-to-VLAN Layer 2 tracingOpen
NetBrain path calculation today supports IP-based, TCP-based, and multicast path types, but does not offer a native path type where the source is a device and the destination is a VLAN for Layer 2 tracing. Customers can approximate this only through a plugin-based workflow that requires manually specifying source device, VLAN, interface, and destination device interface and VLAN, rather than a streamlined native calculation. This enhancement would add a native path type, positioned alongside existing IP and multicast path options, that accepts a source device and destination VLAN and calculates the traversed Layer 2 path across transport technologies such as VPWS, EVPN, Q-in-Q, and standard trunking. Customers operating complex Layer 2 transport environments would gain built-in, consistent path visibility for VLAN-based traffic without relying on plugin workarounds, reducing manual effort during troubleshooting.
API and Authentication Support for New Aruba Central PlatformNot Planned
NetBrain currently supports integration with the classic Aruba Central platform, but does not support the newer Aruba Central platform, which uses a different authentication method and returns API output in a different structure. This enhancement would add a dedicated integration path for the new Aruba Central platform, including its updated authentication flow and API response handling, so that discovery and monitoring can function correctly against it. Customers who have migrated or are migrating to the new Aruba Central platform would gain continued visibility and management capability without being blocked by the underlying platform change.
Add Execution Context (Task, Process ID, Worker Server) to Device Access Audit LogOpen
The Audit Log for Device Access currently records that a device access occurred and when, but does not capture the execution context behind the event. Users have no way to determine which task, process, or worker server initiated a given access without manually cross-referencing multiple server logs. This enhancement would add three fields to each Audit Log for Device Access entry: the triggering task name or type, the associated process ID, and the worker server that executed the task. Providing this execution context would allow administrators and support teams to trace the origin of any device access event directly from the audit log, reducing the time and effort required for troubleshooting.
AI-Suggested Prompts by Topic to Guide New UsersOpen
NetBrain's AI assistant does not currently suggest example prompts or organize them by topic to help users understand what questions they can ask when starting a session. This enhancement would introduce AI-suggested prompts grouped by topic, such as Assets, Cases, and Troubleshooting, presented to users at the start of an AI interaction. Providing these guided starting points would help new users become productive more quickly by clarifying the types of questions the AI feature can answer.
Consistent IPv4 Address Display for MSEE Links in DVTOpen
NetBrain DVT can display an inconsistent view of retrieved IPv4 address data for MSEE links: the address renders correctly on some existing maps but fails to appear on newly created maps for the same device, even though the address is confirmed present in the underlying DVT log. This enhancement would ensure that DVT consistently renders retrieved IPv4 address data for MSEE links regardless of which map instance is used. Consistent display of validated data would help customers trust DVT results and avoid unnecessary troubleshooting caused by display discrepancies.
Enhanced Diagnostics for ServiceNow-NetBrain Connector Health Check FailuresOpen
NetBrain's ServiceNow connector health check currently returns a generic 'Connector is not healthy' timeout message when a connection attempt fails, without providing detail on where the failure occurred, such as the mid server, load balancer, or the NetBrain API service itself. This enhancement would add detailed diagnostic logging and a clearer error breakdown to the connector health check process, allowing administrators to pinpoint the specific point of failure. Customers troubleshooting intermittent or environment-specific connectivity issues between ServiceNow and NetBrain would benefit from reduced diagnostic effort and faster issue resolution.
Export Runbook Templates with Dependent Assets from Automation LibraryOpen
NetBrain currently does not provide a way to export Runbook templates, along with their dependent backend components such as intents and ADT tables, from the Build and Download Library section of the Automation Center. This enhancement proposes adding a native export capability that packages a Runbook template together with its associated automation assets into a single downloadable file. This would allow customers to back up, migrate, or share complete Runbook configurations across environments without manually recreating dependent components, reducing setup effort and the risk of missing dependencies.
Automated ServiceNow Change Request Lifecycle with Scheduling Logic and Reschedule HandlingOpen
NetBrain currently does not support a fully automated end-to-end change management workflow with ServiceNow. Change Requests must be manually triggered, planned dates are not automatically selected based on defined scheduling logic, and reschedule events are not automatically detected or handled. This enhancement would allow NetBrain to automatically trigger Change Request creation in ServiceNow, apply configurable logic to determine the planned implementation date, and detect and respond to reschedule events so that both systems remain synchronized throughout the change lifecycle. Customers would benefit from a consistent, hands-off change management process that reduces manual coordination and scheduling errors between NetBrain and ServiceNow.
Automatic Removal of Decommissioned Devices from Geolocation Dashboard MapsOpen
Geolocation dashboard maps currently can continue to display devices that have already been removed from the domain, even when those devices no longer appear in Data Accuracy Resolution or other inventory views. This creates a discrepancy between the actual device inventory and what is rendered on the geolocation map. This enhancement would have the geolocation dashboard reconcile its device list against current domain inventory each time it refreshes, automatically excluding devices that have been decommissioned or removed. Customers would benefit from accurate, trustworthy dashboard visualizations that reflect the true state of their network without manual intervention to clear stale entries.
Display Advanced Options by Default in Automation Library Share DefinitionOpen
When defining a shared automation library, certain configuration options are currently placed under an advanced section that is collapsed or hidden by default, making them easy to overlook during setup. This enhancement would display these advanced options by default within the share automation library definition screen, rather than requiring users to expand a hidden section. Surfacing these options up front would help administrators configure shared libraries correctly and reduce the risk of missing settings considered important to the library definition.
Reorder Credential Entries in Domain Network SettingsOpen
NetBrain currently adds new credential entries to the bottom of the credentials table in Domain Management Network Settings, with no efficient way to reposition an entry within the list. Administrators who need to move a newly added credential higher in the list must go through a lengthy manual process. This enhancement would introduce a streamlined way to resequence credential entries, such as drag-and-drop reordering or a move-up/move-down control. Customers managing large credential lists would benefit from reduced administrative effort and faster organization of credential priority order.
Separate Command Configuration for Backup and Parsing in Golden AssessmentOpen
NetBrain currently uses the same configuration output for both device backup and Golden Assessment parsing, so customers cannot use one command for backup purposes while relying on a different command for configuration parsing. When a parser is built against output from a different command than the one used for backup, the assessment results are compared against a mismatched baseline, producing inaccurate results. This enhancement would introduce a configuration option that allows the command used for Golden Assessment parsing to be specified independently from the command used for configuration backup. Customers would be able to maintain accurate backups while still leveraging more detailed command output for parsing, ensuring Golden Assessment results reflect the correct baseline comparison.
Comprehensive Site Survey Report for Device and Network Attribute DiscoveryOpen
NetBrain does not currently provide a consolidated site survey report that aggregates detailed device and network attributes across an environment, such as port speed and duplex, PoE usage, transceiver type, estimated fiber mode, VRF and multicast configuration, and voice gateway details. Customers must gather this information through multiple manual steps or separate reports, and there is no built-in way to reconcile discovered devices against an external inventory system to identify discrepancies. This enhancement would introduce a comprehensive site survey report that consolidates these device-level and network-level attributes into a single view, including a discrepancy comparison against an external device list. Customers performing infrastructure audits, capacity planning, or migration readiness assessments would gain a faster, more accurate way to characterize their environment without manual data collection across multiple tools.
Auto Discovery of Switches Connected Behind SD-WAN DevicesOpen
NetBrain's automated discovery task currently fails to detect switches connected behind SD-WAN edge devices, even though these devices can be found through manual discovery. This gap requires administrators to intervene manually on new site turnups to ensure complete device coverage. This enhancement would extend the automated discovery process to reliably identify and include switches situated behind SD-WAN devices during scheduled discovery runs. Customers with distributed SD-WAN site deployments would benefit from complete, accurate topology data without requiring manual discovery steps at each new site.
Automated Detection and Alerting for Asymmetric (Forward/Reverse) Path RoutingOn the Roadmap
NetBrain can visualize a forward path and a reverse path between endpoints, but it does not provide a way to programmatically compare the two paths or determine whether the route is asymmetric. As a result, customers experiencing asymmetric routing issues have no automated way to identify this condition or receive proactive notification when it occurs. This enhancement would introduce distinct forward and reverse path variables, along with the ability to compare devices across the two paths, and would generate an alert when the forward and reverse paths diverge. Automated detection and notification of asymmetric routing would reduce the manual effort required to identify routing inconsistencies and would help customers resolve related application performance and connectivity issues more quickly.
Option to select live or cached data when triggering path calculation from IntentOpen
NetBrain currently does not provide a visible option within Network Intent to trigger a path calculation using either live or cached data. This enhancement would add an explicit control that lets users choose the data source, live or cached, when initiating a path calculation directly from an Intent. Providing this option would give customers greater control over data freshness during troubleshooting and reduce ambiguity about which data set a path calculation is using.
Flexible Condition Logic with Macro Variable Support in Chatbot IntentsOpen
Chatbot intent conditions currently do not support setting or referencing macro variables as part of the condition logic, limiting how adaptable and readable conditional workflows can be. This enhancement would allow users to define macro variables and reference them directly within intent conditions, supporting more flexible branching logic. Customers building complex chatbot automation would benefit from clearer, more maintainable condition structures that reduce the need for rigid, hardcoded logic paths.
Historical Data Analysis for Security Investigation and Threat DetectionOpen
NetBrain currently collects and stores historical network snapshots, but this data cannot be directly analyzed or visualized to support security investigations such as incident response or threat hunting. Security teams lack a way to detect unauthorized changes, unusual connectivity patterns, or configuration deviations by comparing historical network states over time. This enhancement would introduce automated change detection and diff analysis across historical network snapshots, along with AI-assisted anomaly detection to surface unusual paths, new connections, or configuration deviations that may indicate a security breach. Customers would gain the ability to use existing historical data proactively for threat detection and investigation, extending the value of stored network data beyond compliance reporting into broader security operations use cases.
Bulk Move Option for Golden Assessment Rules Between FoldersOpen
NetBrain currently requires users to move Golden Assessment Rules or Features to a different folder one at a time, using an individual 'Move To' action on each item. This becomes impractical when reorganizing large rule sets containing dozens or hundreds of entries. This enhancement would introduce a multi-select bulk move capability within the Golden Assessment Rule list, allowing users to select multiple Assessment Features or Rules and relocate them to a target folder in a single action. Customers managing extensive Golden Assessment libraries would benefit from significantly reduced effort when reorganizing content into logical folder structures.
SNMP Trap Reception for Triggered AutomationOpen
NetBrain currently does not support receiving or processing inbound SNMP traps, and has no mechanism to use trap data as a condition for launching triggered automation. This enhancement would allow NetBrain to receive SNMP traps and provide configuration options for mapping specific trap types or conditions to automation actions, such as running device health checks or other diagnostic intents. For example, a trap indicating a device restart after a power outage could automatically trigger a predefined diagnostic workflow. Customers would benefit from faster, more automated response to network events without requiring a separate trap-processing system to initiate NetBrain automation.
Support Advanced Path Discovery Settings in AI BotOpen
NetBrain's AI Bot currently does not support Advanced Parameter Settings when performing path calculations, which limits its ability to account for conditions such as firewall-blocked traffic that require these settings to resolve correctly. This enhancement would extend AI Bot to recognize and apply Advanced Parameter Settings during path troubleshooting. Supporting these parameters would allow customers to resolve path-related issues directly through AI Bot without needing manual workarounds or escalation to standard path tools.
Region-Based Placement Control for Zero-Touch Map LayoutOpen
NetBrain map templates currently apply general layout rules, but administrators have limited control over where newly discovered devices and interfaces are placed when they are added to an existing, well-organized map. As a result, new devices often appear in random or unhelpful locations, requiring manual repositioning even when a template is in use. This enhancement would allow users to designate a specific region or area of a map as the target location for newly added devices, along with support for standardized left-to-right sequential device alignment and consistent interface connector placement. Customers maintaining large, frequently updated topologies would benefit from a more predictable zero-touch map layout experience, reducing the manual editing currently required to keep maps organized as the network changes.
Connect traceroute origin device to path on mapOpen
NetBrain currently does not connect the originating device to the displayed path when rendering map traceroute results, even when that device is already present on the map. This causes the first hop of the trace to appear disconnected from the rest of the path, creating an incomplete visual representation of the trace. This enhancement would update the map rendering logic to always connect the device where the traceroute was initiated to the resulting path. Ensuring the origin device is properly connected would give customers an accurate, complete view of the traced path, reducing confusion during troubleshooting.
Microsoft Teams Webhook Action Node for Runbook Change NotificationsOpen
NetBrain Runbooks currently have no way to send custom, user-authored messages to a Microsoft Teams channel as part of a change management workflow; existing incident-linked notifications send all components rather than a targeted, custom message. This enhancement would add a Teams webhook action node to the Runbook editor, allowing users to store and select from configured webhooks, choose the target channel, compose a custom message, and trigger delivery at defined points such as change start and change completion. Customers running change processes that rely on a monitored Teams channel would gain a reliable way to communicate change status to stakeholders without manual copy-paste steps or unrelated incident data being sent.
Filter by features
- All features
- AI
- Automation
- Benchmark
- Change Management
- Data Management
- Digital-Twin
- Installation&Deployment
- Integration
- Live Access
- Map
- Multi-Vendor Support
- NetBrain API
- Others
- Path
- Runbook
- System Health Monitoring
- System Management
Login to the community
No account yet? Create an account
Sign in with SSO
Login via NetBrain UniversityEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.