You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WARP client provides diagnostic logs that you can use to troubleshoot connectivity issues on a device.
12
12
@@ -29,9 +29,9 @@ The WARP client provides diagnostic logs that you can use to troubleshoot connec
29
29
30
30
## macOS/Windows/Linux
31
31
32
-
### Retrieve logs
32
+
### Collect logs via the CLI
33
33
34
-
To view WARP logs on desktop devices:
34
+
To collect WARP diagnostic logs on your desktop:
35
35
36
36
<Tabs> <TabItemlabel="macOS">
37
37
@@ -65,9 +65,46 @@ This will place a `warp-debugging-info-<date>-<time>.zip` in the same folder you
65
65
66
66
</TabItem> </Tabs>
67
67
68
-
:::note
69
-
You can also use Digital Experience Monitoring to run `warp-diag` commands on remote devices. For more information, refer to [Remote captures](/cloudflare-one/insights/dex/remote-captures/).
You can collect WARP diagnostic logs remotely from the Zero Trust dashboard by using Digital Experience Monitoring (DEX) [remote captures](/cloudflare-one/insights/dex/remote-captures/).
Cloudflare processes the WARP diagnostic logs that were [captured via the dashboard](#collect-logs-via-the-dashboard) and flags what we determine to be the most important detection events. You can use the WARP diagnostic summary to help you analyze your `warp-diag` logs and identify the root cause of client issues.
83
+
84
+
To access your WARP diagnostic summary:
85
+
86
+
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**.
87
+
2. Locate an existing `warp-diag` log from the list or select **Run diagnostics** to generate a new `warp-diag` log.
88
+
3. Select the three dots for the `warp-diag` log that you want to analyze, then select **View WARP Diag**.
89
+
90
+
The **Overview** tab will display an AI-generated summary of the results, a list of detection events, and basic device information.
91
+
<Detailsheader="Explanation of the fields">
92
+
| Field | Description |
93
+
| ----- | ----------- |
94
+
| Detection type | A common WARP issue that can appear in the diagnostic logs. |
95
+
| Occurences | Number of times an issue was detected in the logs. |
96
+
| Severity level | Indicates the impact of the issue on WARP client functionality. The severity levels are: <ul> <li> **Critical**: Issue causes complete loss of functionality. </li> <li> **Warning**: Issue causes degraded functionality but core features should still work. </li> <li> **No detection**: Issue was not detected in the logs. </li> </ul> |
97
+
| Operating system | OS and OS version of the device. |
98
+
| WARP version | [WARP release version](/cloudflare-one/connections/connect-devices/warp/download-warp/) |
99
+
| Profile ID | [WARP device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/)|
100
+
| Service mode | [WARP mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) |
101
+
| Configuration name | Name of the [Zero Trust organization](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) that WARP is connected to. |
102
+
| Device ID | ID generated by the WARP client. |
103
+
104
+
</Details>
105
+
4. Select a detection type for more information about the event and the recommended next steps.
106
+
107
+
Cloudflare will store the `warp-diag` log and its summary per our [log retention policy](/cloudflare-one/insights/logs/#log-retention). To save a copy onto your local machine, [download the log file](#download-remote-captures) and go to the **JSON file** tab to copy the summary in JSON format.
71
108
72
109
### `warp-diag` logs
73
110
@@ -172,7 +209,7 @@ Always check the timestamps at the end of each log file to verify the time range
0 commit comments