Skip to content

Commit 9e3119d

Browse files
committed
create partial
1 parent 61c9189 commit 9e3119d

File tree

4 files changed

+40
-29
lines changed

4 files changed

+40
-29
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ warp-cli settings
127127

128128
The device profile UUID is shown in the `Profile ID` field.
129129

130-
Alternatively, if you do not have access to the CLI, you can use [DEX remote captures](/cloudflare-one/insights/dex/remote-captures/) to generate a WARP diagnostic log. The `warp-settings.txt` log file will contain the output of `warp-cli settings`.
130+
Alternatively, if you do not have access to the CLI, you can use [DEX remote captures](/cloudflare-one/insights/dex/remote-captures/) to collect WARP diagnostic logs from the Zero Trust dashboard. The device profile UUID is shown in your [WARP diagnostics summary](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/view-warp-diagnostics-summary-beta) under `Profile ID`.
131131

132132
## Selectors
133133

src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx

Lines changed: 3 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: Diagnostic logs
77
---
88

9-
import { TabItem, Tabs, Render, Details, Stream } from "~/components";
9+
import { TabItem, Tabs, Render, Stream } from "~/components";
1010

1111
The WARP client provides diagnostic logs that you can use to troubleshoot connectivity issues on a device.
1212

@@ -77,34 +77,9 @@ You can collect WARP diagnostic logs remotely from the Zero Trust dashboard by u
7777

7878
<Render file="dex/pcaps-download" product="cloudflare-one" />
7979

80-
#### Analyze remote captures (beta)
80+
#### View WARP diagnostics summary (beta)
8181

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" />
10883

10984
### `warp-diag` logs
11085

src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,10 @@ You can analyze `.pcap` files using Wireshark or another third-party packet capt
4242

4343
Refer to [WARP diagnostic logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) for a description of each file.
4444

45+
## View WARP diagnostics summary (beta)
46+
47+
<Render file="dex/pcaps-view-warp-diag" product="cloudflare-one" />
48+
4549
## Limitations
4650

4751
- Packet captures are subject to the following limits:
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
{}
3+
---
4+
5+
import { Details } from "~/components";
6+
7+
The WARP diagnostics summary highlights what Cloudflare determines to be the most important detection events in a `warp-diag` log. You can use the WARP diagnostic summary to help you analyze your `warp-diag` logs and identify the root cause of client issues. WARP diagnostic summaries are only available for logs [collected via the dashboard](#collect-logs-via-the-dashboard).
8+
9+
To access your WARP diagnostic summary:
10+
11+
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**.
12+
2. Locate an existing `warp-diag` log from the list or select **Run diagnostics** to generate a new `warp-diag` log.
13+
3. Select the three dots for the `warp-diag` log that you want to analyze, then select **View WARP Diag**.
14+
15+
The **Overview** tab will display an AI-generated summary of the results, a list of detection events, and basic device information.
16+
<Details header="Explanation of the fields">
17+
| Field | Description |
18+
| ----- | ----------- |
19+
| Detection type | A common WARP issue that can appear in the diagnostic logs. |
20+
| Occurences | Number of times an issue was detected in the logs. |
21+
| 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> |
22+
| Operating system | OS and OS version of the device. |
23+
| WARP version | [WARP release version](/cloudflare-one/connections/connect-devices/warp/download-warp/) |
24+
| Profile ID | [WARP device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/) UUID|
25+
| Service mode | [WARP mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) |
26+
| Configuration name | Name of the [Zero Trust organization](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) that WARP is connected to. |
27+
| Device ID | ID generated by the WARP client. |
28+
29+
</Details>
30+
4. Select a detection type for more information about the event and recommended next steps.
31+
32+
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.

0 commit comments

Comments
 (0)