Review the open issues in Prisma Access Insights.
These are the issues we’re currently working on.
On the Remote Networks Site Details page, the linear scale toggle is missing from the
Tunnel Bandwidth & Round Trip Timecharts.
Upon clicking on the key icon next to the tenant name to generate an API key, the /apikey feature returns HTTP 400.
The mu_auth_success_count_histogram and mu_auth_failure_count_histogram APIs are not considering unique usernames in a bin per Prisma Access Location.
The user_location_search_contains API is not returning data when passing complete location name. The UI is supposed to show
City, Country, but
Countryinformation is not always returned.
A user’s GlobalProtect version changes within a single session.
On the Mobile Users - GlobalProtect page, the device count in the
Devices of Connected Userswidget and the GlobalProtect version distribution on the
Monitoring Summarypage do not match.
The Auth Profile for all Mobile Users appears as Unknown.
The Prisma Access Location is not showing up on the Mobile Users Map View on Prisma Access Insights for ZTNA tenants but it showing up on the Executive Summary Map View. Upon further inspection, we see that the /connected_user_global_map API is not returning the locations.
Disconnected mobile user messages are not created for some login sessions.
Remote Networks > Site List, IPSec termination node utilization details are not loading when first selected.
Mobile User - GlobalProtect > Site List,
Remote Networks > Site List, and
Service Connections > Site List, an error occurs when you select a
Prisma Access Locationname.
Mobile Users - GlobalProtectpage, the
Current Connected Usersand
Connected Userswidgets, some column headings show incorrect names with underscores.
Remote Networks Dashboardand
Service Connections Dashboardpages, the
Total Sitestable may show nodes in the
Prisma Access Nodecolumn as being
Up. However, when you select that site’s
Prisma Access Locationand go to the
Prisma Access Locationtable, the
Location Status for Remote Networksand
Location Status for Service Connectionsshow that the node status is
Mobile Users - GlobalProtectpage, the
GlobalProtect Version Distributionand
Mobile User License Consumptionwidgets are using last_n_days instead of time filter changes in which event_time is calculated by the UI.
In the Aggregated Tunnel Connectivity Trend Over Time widget on the
Tunnelsdashboard, the time range filter is applied so all tunnels are fetched regardless of the state.
Alertsseverity filter is not working correctly. It does not reflect new status when an alert’s severity is changed.
Explicit Proxy information does not display in Insights for Cloud Managed Prisma Access deployments.
In a notification profile, there is no way to delete a webhook once the webhook has been added. Currently, if a customer wants to delete a webhook, they have to delete the notification profile and re-create it without the webhook. Alternatively, a customer can choose to disable the profile if they do not wish to receive alert notifications.
If you click on the group name to retrieve the users who belong to the group, occasionally you may not get a response back with an error saying ‘Failed to fetch data’. This could happen when the group has more than 50,000 users.
Connected Userswidget on
Monitoring Summarytab on the
Mobile Usersdashboard, toggling between
Averageusers for Explicit Proxy users does not work.
If multiple user connections that use Explicit Proxy to connect to Prisma Access have the same source IP display as duplicate records if the browser version is same.
Alerts are not supported for Mobile Users using Explicit Proxy to connect to Prisma Access. However, you can see the performance data for such users in the widgets.
Service Connectionsection of the
License Expiration Dateswidget in the
Summarydashboard does not display the Service Connection license information for a tenant even though the tenant may have a
Recommended For You
Recommended videos not found.