GlobalProtect App Log Collection for Troubleshooting Overview
Learn how to quickly resolve mobile user connection, performance, and access issues by configuring the GlobalProtect app to send troubleshooting and diagnostic logs from the end user’s endpoint to Cortex Data Lake.
With Prisma Access and next-generation firewall deployments, you can now quickly resolve mobile user connection, performance, and access issues. The GlobalProtect app can now be configured to send troubleshooting and diagnostic logs from the end user’s endpoint to Cortex Data Lake for further analysis. By using this feature, when the end user reports an issue from the GlobalProtect app (upon user request), the app can generate and send an easy to read, comprehensive report to help you to quickly identify the root cause of the remote end user issue. Additionally, the GlobalProtect app can run end-to-end diagnostic tests to probe the state and performance of the network connection and the performance of specific web applications from the remote end user’s endpoint. This results in faster resolution of the remote end user issues, enables increased productivity, and optimizes the user experience for the remote end user. End users can now report an issue from their endpoint directly to Cortex Data Lake to which the administrator can access without manually collecting and sending the GlobalProtect app logs, for example, through email or storing them on a cloud drive. If end users consent to run diagnostic tests and to include diagnostic logs on the GlobalProtect app, the troubleshooting log bundle and diagnostic logs are sent to Cortex Data Lake from their endpoint so you can review them easily using the Explore app on the hub. If end users do not consent to run diagnostic tests and to include diagnostic logs and troubleshooting logs on the GlobalProtect app, only troubleshooting reports without the troubleshooting log bundle are sent to Cortex Data Lake from their endpoint for further analysis. For example, if you want to run diagnostic tests for HTTPS-based destination URLs that can contain IP addresses or fully qualified domain names (for example, https://10.10.10.10/resource.html, https://webserver/file.pdf, or https://google.com) to determine whether there is an issue with latency or network performance, you can configure these HTTPS-based destination URLs that are critical to your end user’s productivity by enabling the GlobalProtect app log collection for troubleshooting on the portal. By default, the GlobalProtect app log collection for troubleshooting is disabled, and as a result, end users cannot send troubleshooting and diagnostic logs to Cortex Data Lake from their endpoint. They would have to manually collect and send the GlobalProtect app logs to the administrator for troubleshooting and debugging purposes.
The following diagram illustrates the workflow for sending the GlobalProtect app troubleshooting reports and diagnostic logs from the end user’s endpoint to Cortex Data Lake:
Before you begin to enable the GlobalProtect app log collection for troubleshooting and to view the GlobalProtect app troubleshooting and diagnostic log records on the Explore app, follow these recommendations to communicate:
- Retrieve the Cortex Data Lake certificate.
Recommended For You
Recommended videos not found.