|
6 | 6 | label: Diagnostic logs |
7 | 7 | --- |
8 | 8 |
|
9 | | -import { TabItem, Tabs, Render, Details, Stream } from "~/components"; |
| 9 | +import { TabItem, Tabs, Render, Stream } from "~/components"; |
10 | 10 |
|
11 | 11 | The WARP client provides diagnostic logs that you can use to troubleshoot connectivity issues on a device. |
12 | 12 |
|
@@ -77,34 +77,9 @@ You can collect WARP diagnostic logs remotely from the Zero Trust dashboard by u |
77 | 77 |
|
78 | 78 | <Render file="dex/pcaps-download" product="cloudflare-one" /> |
79 | 79 |
|
80 | | -#### Analyze remote captures (beta) |
| 80 | +#### View WARP diagnostics summary (beta) |
81 | 81 |
|
82 | | -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 | | - <Details header="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. |
| 82 | +<Render file="dex/pcaps-view-warp-diag" product="cloudflare-one" /> |
108 | 83 |
|
109 | 84 | ### `warp-diag` logs |
110 | 85 |
|
|
0 commit comments