From 29b93ff17a4049913235ea4ffc85a5e168168bb8 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Mon, 23 Sep 2024 20:16:27 -0400
Subject: [PATCH 01/10] list new warp-diag files

---
 .../warp/troubleshooting/warp-logs.mdx        | 114 +++++++++++-------
 1 file changed, 71 insertions(+), 43 deletions(-)

diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
index 6cd748402eedbe..e05e6028ee3c3d 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
@@ -1,6 +1,6 @@
 ---
 pcx_content_type: reference
-title: Debug logs
+title: Diagnostic logs
 sidebar:
   order: 7
 ---
@@ -13,7 +13,7 @@ The WARP client provides diagnostic logs that you can use to troubleshoot connec
 
 ### Retrieve logs
 
-To view debug logs on desktop devices:
+To view WARP logs on desktop devices:
 
 <Tabs> <TabItem label="macOS">
 
@@ -47,50 +47,78 @@ This will place a `warp-debugging-info-<date>-<time>.zip` in the same folder you
 
 </TabItem> </Tabs>
 
+:::note
+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/).
+:::
+
 ### `warp-diag` logs
 
 The `warp-debugging-info-<date>-<time>.zip` archive contains the following files:
 
-| File name                                                                                           | Description                                                                                                                                                                                                                                                                                                                                 |
-| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `boringtun.log`                                                                                     | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network.                                                                                                                                                                                                                                                 |
-| `connectivity.txt`                                                                                  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#connectivity-check).                                                                                                                                                                     |
-| `daemon.log`                                                                                        | Detailed log of all actions performed by the WARP client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.                                                                                                                                                      |
-| `daemon_dns.log`                                                                                    | Contains detailed DNS logs if **Log DNS queries** was enabled on WARP.                                                                                                                                                                                                                                                                      |
-| `date.txt`                                                                                          | Date and time (UTC) when you ran the `warp-diag` command.                                                                                                                                                                                                                                                                                   |
-| `dns-check.txt`                                                                                     | Verifies that the WARP DNS servers are set as system default. For [operating modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) where DNS filtering is enabled, this file contains the IPs of the local WARP DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dns_stats.log`                                                                                     | Statistics on the DNS queries received and resolved by WARP, generated every two minutes.                                                                                                                                                                                                                                                   |
-| `etc-hosts.txt`                                                                                     | Static DNS config of device.                                                                                                                                                                                                                                                                                                                |
-| `gui-launcher.log`                                                                                  | macOS console log showing application launch                                                                                                                                                                                                                                                                                                |
-| `gui-log.log`                                                                                       | Log file for the GUI app that users interact with.                                                                                                                                                                                                                                                                                          |
-| `hostname.txt`                                                                                      | Name of the device.                                                                                                                                                                                                                                                                                                                         |
-| `ifconfig.txt` <br/> `ipconfig.txt`                                                                 | IP configuration of each network interface.                                                                                                                                                                                                                                                                                                 |
-| `installer.log`                                                                                     | MSI or PKG installation log                                                                                                                                                                                                                                                                                                                 |
-| `local_policy_redacted.txt`                                                                         | [Managed deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) on the device.                                                                                                                                                                                                      |
-| `netstat.txt` <br/> `routetable.txt`                                                                | Routing table used by the device.                                                                                                                                                                                                                                                                                                           |
-| `netstat-v6.txt`                                                                                    | IPv6 routing table (Linux only).                                                                                                                                                                                                                                                                                                            |
-| `platform.txt`                                                                                      | Operating system of the device.                                                                                                                                                                                                                                                                                                             |
-| `ps.txt` <br/> `processes.txt`                                                                      | List of all active processes on the device when `warp-diag` was run.                                                                                                                                                                                                                                                                        |
-| `resolv.conf`                                                                                       | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured.                                                                                                                                                                                                                                          |
-| `route.txt`                                                                                         | Output from the `route get` command used to verify that network traffic is going over the correct interface.                                                                                                                                                                                                                                |
-| `scutil-dns.txt`                                                                                    | DNS configuration on Mac/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                    |
-| `scutil-proxy.txt`                                                                                  | Proxy configuration on Mac/Linux (available in `ipconfig.txt` on Windows).                                                                                                                                                                                                                                                                  |
-| `stats.log`                                                                                         | Uptime and throughput stats for the WARP tunnel, generated every two minutes.                                                                                                                                                                                                                                                               |
-| `sw-vers.txt`                                                                                       | Operating system of the device.                                                                                                                                                                                                                                                                                                             |
-| `sysinfo.json`                                                                                      | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.                                                                                                                                                                                                 |
-| `systeminfo.txt` <br/> `system-profile.txt`                                                         | System software overview.                                                                                                                                                                                                                                                                                                                   |
-| `timezone.txt`                                                                                      | Local timezone of the device specified as a UTC offset.                                                                                                                                                                                                                                                                                     |
-| `traceroute.txt`                                                                                    | Traceroute to the [WARP ingress IPs](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network.                                                                                                                                                |
-| `uname.txt`                                                                                         | Linux-only system information including kernel version.                                                                                                                                                                                                                                                                                     |
-| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.                                                                                                                                                                                                                                                                                             |
-| `version.txt`                                                                                       | [WARP client version](/cloudflare-one/connections/connect-devices/warp/download-warp/) installed on the device.                                                                                                                                                                                                                             |
-| `warp-account.txt`                                                                                  | WARP client device enrollment information.                                                                                                                                                                                                                                                                                                  |
-| `warp-device-posture.txt`                                                                           | [Device posture data](/cloudflare-one/identity/devices/warp-client-checks/) obtained by the WARP client.                                                                                                                                                                                                                                    |
-| `warp-dns-stats.txt`                                                                                | Summary of recent DNS queries on the device since `dns-stats.log` was generated.                                                                                                                                                                                                                                                            |
-| `warp-network.txt`                                                                                  | Network settings on the device detected by WARP.                                                                                                                                                                                                                                                                                            |
-| `warp-settings.txt`                                                                                 | [WARP client settings](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/) applied to the device.                                                                                                                                                                                                               |
-| `warp-stats.txt`                                                                                    | Uptime and throughput of the WARP tunnel since `stats.log` was generated.                                                                                                                                                                                                                                                                   |
-| `warp-status.txt`                                                                                   | Status of WARP switch (`Connected` or `Disconnected`).                                                                                                                                                                                                                                                                                      |
+| File name  | Description   |
+| --- | --- |
+| `alternate-networks-check.txt` | |
+| `boringtun.log` | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network. |
+| `bound-dns-ports.txt` | |
+| `captive-portal-hotspot-detect.txt` | |
+| `connectivity.txt`  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#connectivity-check).|
+| `daemon_dns.log` | Contains detailed DNS logs if **Log DNS queries** was enabled on WARP.  |
+| `daemon.log`                                                                                        | Detailed log of all actions performed by the WARP client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.   |
+| `date.txt`  | Date and time (UTC) when you ran the `warp-diag` command.  |
+| `dex.log`  |  |
+| `dhcp-lease-plists.txt`  |  |
+| `dhcp-lease.txt`  |  |
+| `dig.txt`  |  |
+| `dns_stats.log`  | Statistics on the DNS queries received and resolved by WARP, generated every two minutes.  |
+| `dns-check.txt` | Verifies that the WARP DNS servers are set as system default. For [operating modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) where DNS filtering is enabled, this file contains the IPs of the local WARP DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
+| `dynamic.log` | |
+| `etc-hosts.txt`  | Static DNS config of device.  |
+| `firewall-pfctl-all.txt` | |
+| `firewall-rules.txt` | |
+| `gui-launcher.log` | macOS console log showing application launch  |
+| `gui-log.log`  | Log file for the GUI app that users interact with. |
+| `hostname.txt` | Name of the device.  |
+| `ifconfig.txt` <br/> `ipconfig.txt`  | IP configuration of each network interface.  |
+| `installed_applications.text` | |
+| `installed_cert.pem` | |
+| `installer.log` <br/> `InstallHistory.plist` <br/> `msi-installer.log` <br/> `macos_installer.log` | MSI or PKG installation logs  |
+| `ipc.log` | |
+| `lauchd-dumpstate.txt` | |
+| `local_policy.redacted.txt` | [Managed deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) on the device. |
+| `netstat.txt` <br/> `routetable.txt` | Routing table used by the device.  |
+| `netstat-v6.txt` | IPv6 routing table (Linux only). |
+| `platform.txt` | Operating system of the device.  |
+| `ps.txt` <br/> `processes.txt` | List of all active processes on the device when `warp-diag` was run.  |
+| `resolv.conf` | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured. |
+| `route.txt` | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration. |
+| `scutil-dns.txt` | DNS configuration on Mac/Linux (available in `ipconfig.txt` on Windows).  |
+| `scutil-networkinfo.txt` | ? (available in `interfaces-config.txt` on Windows). |
+| `scutil-proxy.txt` | Proxy configuration on Mac/Linux (available in `ipconfig.txt` on Windows).  |
+| `snapshots-collection.log` | |
+| `stats.log`  | Uptime and throughput stats for the WARP tunnel, generated every two minutes.  |
+| `sw-vers.txt`  | Operating system of the device.  |
+| `sysinfo.json` | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.  |
+| `system-extension-diagnostics.txt` | |
+| `systeminfo.txt` <br/> `system-profile.txt` | System software overview.  |
+| `taskdump.log` | |
+| `timezone.txt`  | Local timezone of the device specified as a UTC offset. |
+| `traceroute.txt` | Traceroute to the [WARP ingress IPs](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network. |
+| `uname.txt`  | Linux-only system information including kernel version. |
+| `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.   |
+| `version.txt`  | [WARP client version](/cloudflare-one/connections/connect-devices/warp/download-warp/) installed on the device. |
+| `warp-account.txt` | WARP client device enrollment information.  |
+| `warp-bus-metrics.txt` | |
+| `warp-device-posture.txt` | [Device posture data](/cloudflare-one/identity/devices/warp-client-checks/) obtained by the WARP client. |
+| `warp-dex-data.txt` | |
+| `warp-dns-fallbacks.txt` | |
+| `warp-dns-lock.json` | |
+| `warp-dns-stats.txt` | Summary of recent DNS queries on the device since `dns-stats.log` was generated.  |
+| `warp-network.txt` | Network settings on the device detected by WARP.  |
+| `warp-settings.txt`  | [WARP client settings](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/) applied to the device.  |
+| `warp-stats.txt` | Uptime and throughput of the WARP tunnel since `stats.log` was generated. |
+| `warp-status.txt` | Status of WARP switch (`Connected` or `Disconnected`). |
+| `wdutil-info.txt` | |
+| `xpc-launchd.log` | |
 
 #### Multiple versions of the same log
 
@@ -109,7 +137,7 @@ In timestamped logs such as `daemon.log`, the most recent events will appear at
 
 ### Retrieve logs
 
-To view debug logs on mobile devices:
+To view WARP logs on mobile devices:
 
 1. Open the 1.1.1.1 app.
 2. Go to **Settings** > **Advanced** > **Diagnostics**.

From 05e5d7c2d979556399084c0c7dcf9667b912552f Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Mon, 23 Sep 2024 20:16:39 -0400
Subject: [PATCH 02/10] account limits

---
 src/content/docs/cloudflare-one/account-limits.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index 27267e589ad0dc..b6c8a81f1911f8 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -65,7 +65,9 @@ This page lists the default account limits for rules, applications, fields, and
 
 | Feature           | Limit |
 | ----------------- | ----- |
-| Tests per account | 10    |
+| HTTP or Traceroute tests per account | 10    |
+| Remote captures per day |  800 |
+| Unique devices tested by remote captures per day | 10 |
 
 ## Maximum number of characters
 

From 0124ae8a4e1117a4315af6b0ccd8787945975548 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Mon, 23 Sep 2024 20:16:52 -0400
Subject: [PATCH 03/10] new remote captures page

---
 .../insights/dex/notifications.mdx            |  2 +-
 .../insights/dex/remote-captures.mdx          | 68 +++++++++++++++++++
 2 files changed, 69 insertions(+), 1 deletion(-)
 create mode 100644 src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx

diff --git a/src/content/docs/cloudflare-one/insights/dex/notifications.mdx b/src/content/docs/cloudflare-one/insights/dex/notifications.mdx
index e118d6ab36b44a..c784810126e13a 100644
--- a/src/content/docs/cloudflare-one/insights/dex/notifications.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/notifications.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Notifications
 sidebar:
-  order: 3
+  order: 5
 head:
   - tag: title
     content: DEX notifications
diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
new file mode 100644
index 00000000000000..828b469dc5fa51
--- /dev/null
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -0,0 +1,68 @@
+---
+pcx_content_type: reference
+title: Remote captures
+sidebar:
+  order: 4
+
+---
+
+import { Details, Render } from "~/components"
+
+
+<Details header="Feature availability">
+
+| [WARP modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) | [Zero Trust plans](https://www.cloudflare.com/teams-pricing/) |
+| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
+| All modes                                                                                 | All plans                                                     |
+
+| System   | Availability | Minimum WARP version |
+| -------- | ------------ | -------------------- |
+| Windows  | ✅            | 2024.6.415.0         |
+| macOS    | ✅            |                      |
+| Linux    | ✅            |                      |
+| iOS      | ❌            |                      |
+| Android  | ❌            |                      |
+| ChromeOS | ❌            |                      |
+
+</Details>
+
+Remote captures allow administrators to collect packet captures (PCAPs) and WARP diagnostic logs directly from end user devices. This data can be used to troubleshoot network problems, investigate security incidents, and identify performance bottlenecks.
+
+## Start a remote capture
+
+To capture data from a remote device:
+
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**.
+2. Select the device(s) you want to run a capture on. Devices must be [registered](/cloudflare-one/connections/connect-devices/warp/deployment/) in your Zero Trust organization.
+3. Configure the types of captures to run.
+	- **PCAP**: Performs packet captures by running `warp-cli debug pcap start` and `warp-cli debug pcap stop` commands on the device. The capture will include two files -- a PCAP for traffic outside of the WARP tunnel (default network interface), and a PCAP for traffic inside of the WARP tunnel ([WARP virtual interface](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic)).
+		<Details header="PCAP limits">
+		Packet captures are subject to the following limits:
+			- **Maximum time limit**: 1,800 seconds
+			- **Maximum file size**: 100 MB
+			- **Maximum packet size**: 160 bytes
+		</Details>
+	- **WARP Diagnostics Logs**: Generates [WARP diagnostic logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) by running a `warp-diag` command on the device. You can optionally select **Test all routes** to run an `ip route get` command for all IPs and domains in your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/).
+4. Select **Start a capture**.
+
+DEX will now send capture requests to the configured devices. If the WARP client is disconnected, the capture will time out after 10 minutes.
+
+## Check remote capture status
+
+To view a list of captures, go to **DEX** > **Remote captures**. The **Status** column displays one of the following options:
+	- **Success**: The capture is complete and ready for download.
+	- **Running**: The capture is in progress on the device.
+	- **Pending Upload**: The capture is complete but not yet ready for download.
+	- **Failed**: The capture has either timed out or encountered an error. To retry the capture, make sure the WARP client is connected and start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture).
+
+## Download remote captures
+
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**.
+2. Find a successful capture.
+3. Select the three-dot menu and select **Download**.
+
+This will download a ZIP file to your local machine. You can analyze `.pcap` files using Wireshark or another third-party packet capture tool.
+
+## Data retention
+
+Cloudflare will store capture data for 7 days.
\ No newline at end of file

From 625635accd0a69e8491497651938062b2d8af703 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Wed, 25 Sep 2024 15:44:45 -0400
Subject: [PATCH 04/10] update plan limits

---
 src/content/docs/cloudflare-one/account-limits.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/content/docs/cloudflare-one/account-limits.mdx b/src/content/docs/cloudflare-one/account-limits.mdx
index b6c8a81f1911f8..20698147c6814f 100644
--- a/src/content/docs/cloudflare-one/account-limits.mdx
+++ b/src/content/docs/cloudflare-one/account-limits.mdx
@@ -65,9 +65,11 @@ This page lists the default account limits for rules, applications, fields, and
 
 | Feature           | Limit |
 | ----------------- | ----- |
-| HTTP or Traceroute tests per account | 10    |
-| Remote captures per day |  800 |
-| Unique devices tested by remote captures per day | 10 |
+| Tests per account | 10    |
+| Remote captures per day (Free users)  |  100 |
+| Remote captures per day (Pay-as-you-go users)  |  200 |
+| Remote captures per day (Enterprise users)  |  800 |
+
 
 ## Maximum number of characters
 

From 67a0e5fa7c8b06aee73f01615dea92c9908e0415 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Wed, 25 Sep 2024 16:16:12 -0400
Subject: [PATCH 05/10] remove CLI commands

---
 .../insights/dex/remote-captures.mdx            | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
index 828b469dc5fa51..ac37541682cc2b 100644
--- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -33,16 +33,19 @@ Remote captures allow administrators to collect packet captures (PCAPs) and WARP
 To capture data from a remote device:
 
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**.
-2. Select the device(s) you want to run a capture on. Devices must be [registered](/cloudflare-one/connections/connect-devices/warp/deployment/) in your Zero Trust organization.
+2. Select up to 10 devices that you want to run a capture on. Devices must be [registered](/cloudflare-one/connections/connect-devices/warp/deployment/) in your Zero Trust organization.
 3. Configure the types of captures to run.
-	- **PCAP**: Performs packet captures by running `warp-cli debug pcap start` and `warp-cli debug pcap stop` commands on the device. The capture will include two files -- a PCAP for traffic outside of the WARP tunnel (default network interface), and a PCAP for traffic inside of the WARP tunnel ([WARP virtual interface](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic)).
-		<Details header="PCAP limits">
+	- **PCAP**: Performs packet captures for traffic outside of the WARP tunnel (default network interface) and traffic inside of the WARP tunnel ([WARP virtual interface](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic)).
+		<Details header="PCAP capture limits">
 		Packet captures are subject to the following limits:
-			- **Maximum time limit**: 1,800 seconds
-			- **Maximum file size**: 100 MB
-			- **Maximum packet size**: 160 bytes
+			- **Maximum time limit**: 600 seconds
+			- **Maximum file size**: 50 MB
+			- **Maximum packet size**: 1500 bytes
+		</Details>
+	- **WARP Diagnostics Logs**: Generates a [WARP diagnostic log](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) of the past 96 hours. To include a routing test for all IPs and domains in your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/), select **Test all routes**.
+		<Details header="WARP capture limits">
+		WARP diagnostic logs have no file size limit, but files larger than 100 MB cannot be uploaded to Cloudflare and must be shared directly with the admin.
 		</Details>
-	- **WARP Diagnostics Logs**: Generates [WARP diagnostic logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) by running a `warp-diag` command on the device. You can optionally select **Test all routes** to run an `ip route get` command for all IPs and domains in your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/).
 4. Select **Start a capture**.
 
 DEX will now send capture requests to the configured devices. If the WARP client is disconnected, the capture will time out after 10 minutes.

From 309e3aad69375dc0a38423bf0ac094317fcbf464 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Thu, 10 Oct 2024 17:01:16 -0400
Subject: [PATCH 06/10] warp versions

---
 .../docs/cloudflare-one/insights/dex/remote-captures.mdx    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
index ac37541682cc2b..135af47855c559 100644
--- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -17,9 +17,9 @@ import { Details, Render } from "~/components"
 
 | System   | Availability | Minimum WARP version |
 | -------- | ------------ | -------------------- |
-| Windows  | ✅            | 2024.6.415.0         |
-| macOS    | ✅            |                      |
-| Linux    | ✅            |                      |
+| Windows  | ✅            | 2024.9.346.0        |
+| macOS    | ✅            | 2024.9.346.0        |
+| Linux    | ✅            | 2024.9.346.0        |
 | iOS      | ❌            |                      |
 | Android  | ❌            |                      |
 | ChromeOS | ❌            |                      |

From cb4811c22bc6aa2ea5dd8a833ca24c8dce4d3fc6 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Thu, 10 Oct 2024 17:01:28 -0400
Subject: [PATCH 07/10] add warp-diag files

---
 .../warp/troubleshooting/warp-logs.mdx        | 71 ++++++++++---------
 1 file changed, 39 insertions(+), 32 deletions(-)

diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
index e05e6028ee3c3d..0bb873a0e95d38 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
@@ -57,68 +57,75 @@ The `warp-debugging-info-<date>-<time>.zip` archive contains the following files
 
 | File name  | Description   |
 | --- | --- |
-| `alternate-networks-check.txt` | |
+| `.qlog`| QLog files used to debug MASQUE connection issues.|
+| `.pcap` | Packet capture (PCAP) files that were manually generated using `warp-cli debug pcap` commands. |
+| `alternate-networks-check.txt` | Connectivity status for each [managed network](/cloudflare-one/connections/connect-devices/warp/configure-warp/managed-networks/). |
 | `boringtun.log` | Log for the WARP tunnel that serves traffic from the device to Cloudflare's global network. |
-| `bound-dns-ports.txt` | |
-| `captive-portal-hotspot-detect.txt` | |
-| `connectivity.txt`  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#connectivity-check).|
-| `daemon_dns.log` | Contains detailed DNS logs if **Log DNS queries** was enabled on WARP.  |
+| `bound-dns-ports.txt` | Active processes on port `53`.  |
+| `captive-portal-hotspot-detect.txt` | HTTP response of `captive.apple.com`|
+| `connectivity.txt`  | DNS resolution and HTTP trace requests to [validate a successful connection](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#connectivity-check). Can be used to determine whether traffic is routing through the WARP tunnel. |
+| `daemon_dns.log` | Contains detailed DNS logs if **Log DNS queries** is enabled in the WARP client. |
 | `daemon.log`                                                                                        | Detailed log of all actions performed by the WARP client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.   |
 | `date.txt`  | Date and time (UTC) when you ran the `warp-diag` command.  |
-| `dex.log`  |  |
-| `dhcp-lease-plists.txt`  |  |
-| `dhcp-lease.txt`  |  |
-| `dig.txt`  |  |
+| `dex.log`  | ? |
+| `dhcp-lease-plists.txt`  | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease. |
+| `dhcp-lease.txt`  | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux). |
+| `dig.txt`  | DNS lookup query output for `cloudflare.com` and `apple.com`. |
 | `dns_stats.log`  | Statistics on the DNS queries received and resolved by WARP, generated every two minutes.  |
 | `dns-check.txt` | Verifies that the WARP DNS servers are set as system default. For [operating modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) where DNS filtering is enabled, this file contains the IPs of the local WARP DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log` | |
+| `dynamic.log` | ? |
 | `etc-hosts.txt`  | Static DNS config of device.  |
-| `firewall-pfctl-all.txt` | |
-| `firewall-rules.txt` | |
-| `gui-launcher.log` | macOS console log showing application launch  |
+| `firewall-pfctl-all.txt` | Packet filter (pf) firewall configuration (macOS only). |
+| `firewall-rules.txt` | The [system firewall rules](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#system-firewall) configured by WARP. |
+| `gui-launcher.log` | macOS console log showing application launch.  |
 | `gui-log.log`  | Log file for the GUI app that users interact with. |
 | `hostname.txt` | Name of the device.  |
 | `ifconfig.txt` <br/> `ipconfig.txt`  | IP configuration of each network interface.  |
-| `installed_applications.text` | |
-| `installed_cert.pem` | |
-| `installer.log` <br/> `InstallHistory.plist` <br/> `msi-installer.log` <br/> `macos_installer.log` | MSI or PKG installation logs  |
-| `ipc.log` | |
-| `lauchd-dumpstate.txt` | |
-| `local_policy.redacted.txt` | [Managed deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) on the device. |
+| `installed_applications.text` | List of installed applications. |
+| `installed_cert.pem` | [Root certificate](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/) installed on the system. |
+| `installer.log` <br/> `msi-installer.log` | MSI or PKG installation log.|
+| `InstallHistory.plist` <br/> `macos_installer.log` | macOS software installation logs. |
+| `ipc.log` | Logs IPC communication between the GUI and daemon. Useful for situations where the GUI crashes or is unable to communicate with the daemon. |
+| `kernel-modules.txt` | List of loaded kernel modules (macOS and Linux) or drivers (Windows).|
+| `launchd-dumpstate.txt` | Current state of the macOS `launchd system` including the loaded jobs, their status, and dependencies. |
+| `local_policy.redacted.txt`<br/> `mdm.plist` <br/> `mdm.xml`| [Managed deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) on the device. |
+| `lsb-release.txt` |  Output from the `lsb_release` command (Linux only). |
 | `netstat.txt` <br/> `routetable.txt` | Routing table used by the device.  |
 | `netstat-v6.txt` | IPv6 routing table (Linux only). |
 | `platform.txt` | Operating system of the device.  |
 | `ps.txt` <br/> `processes.txt` | List of all active processes on the device when `warp-diag` was run.  |
 | `resolv.conf` | The contents of the `/etc/resolv.conf` file on Mac/Linux, where system DNS servers are configured. |
 | `route.txt` | Output from the `ip route get` command, used to verify that network traffic is going over the correct interface. You can optionally use the `warp-diag --enable-all-routes` flag to include tests for all IPs and domains in your Split Tunnel configuration. |
-| `scutil-dns.txt` | DNS configuration on Mac/Linux (available in `ipconfig.txt` on Windows).  |
-| `scutil-networkinfo.txt` | ? (available in `interfaces-config.txt` on Windows). |
-| `scutil-proxy.txt` | Proxy configuration on Mac/Linux (available in `ipconfig.txt` on Windows).  |
-| `snapshots-collection.log` | |
+| `scutil-dns.txt` | DNS configuration on macOS/Linux (available in `ipconfig.txt` on Windows).  |
+| `scutil-networkinfo.txt` | IPv4 and IPv6 network interface configuration on macOS (available in `interfaces-config.txt` on Windows). |
+| `scutil-proxy.txt` | Proxy configuration on macOS/Linux (available in `ipconfig.txt` on Windows).  |
+| `snapshots-collection.log` | Logs generated when collecting `snapshots/*.log`. Used to debug why WARP failed to collect a snapshot. |
+| `snapshots/*.log` | Diagnostics generated when an error occurs. |
 | `stats.log`  | Uptime and throughput stats for the WARP tunnel, generated every two minutes.  |
 | `sw-vers.txt`  | Operating system of the device.  |
 | `sysinfo.json` | CPU and memory usage when `warp-diag` was run. This information is useful for determining whether slow speeds are due to heavy system load.  |
-| `system-extension-diagnostics.txt` | |
+| `system-extension-diagnostics.txt` | Status and health of loaded system extensions (macOS only). |
 | `systeminfo.txt` <br/> `system-profile.txt` | System software overview.  |
-| `taskdump.log` | |
+| `System.evtx` | Windows system event log. |
+| `taskdump.log` | If the daemon hangs, this file will contain a dump of the currently running processes. This is helpful in debugging hangs, deadlocks, and tasks. |
 | `timezone.txt`  | Local timezone of the device specified as a UTC offset. |
 | `traceroute.txt` | Traceroute to the [WARP ingress IPs](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) showing the path from the device to Cloudflare's global network. |
 | `uname.txt`  | Linux-only system information including kernel version. |
 | `v4interfaces.txt` <br/> `v4subinterfaces.txt` <br/> `v6interfaces.txt` <br/> `v6subinterfaces.txt` | IPv4 and IPv6 network configuration on Windows.   |
 | `version.txt`  | [WARP client version](/cloudflare-one/connections/connect-devices/warp/download-warp/) installed on the device. |
 | `warp-account.txt` | WARP client device enrollment information.  |
-| `warp-bus-metrics.txt` | |
-| `warp-device-posture.txt` | [Device posture data](/cloudflare-one/identity/devices/warp-client-checks/) obtained by the WARP client. |
-| `warp-dex-data.txt` | |
-| `warp-dns-fallbacks.txt` | |
-| `warp-dns-lock.json` | |
+| `warp-bus-metrics.txt` | Metrics for the internal message bus framework used by the WARP client. |
+| `warp-device-posture.txt` | Current [device posture](/cloudflare-one/identity/devices/warp-client-checks/) status. |
+| `warp-dex-data.txt` | Currently configured [DEX tests](/cloudflare-one/insights/dex/tests/) and their most recent statuses. |
+| `warp-dns-fallbacks.txt` | List of default DNS fallbacks used by the WARP DNS proxy. |
+| `warp-dns-lock.json` | Default DNS providers and network interface information. |
 | `warp-dns-stats.txt` | Summary of recent DNS queries on the device since `dns-stats.log` was generated.  |
 | `warp-network.txt` | Network settings on the device detected by WARP.  |
 | `warp-settings.txt`  | [WARP client settings](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/) applied to the device.  |
 | `warp-stats.txt` | Uptime and throughput of the WARP tunnel since `stats.log` was generated. |
 | `warp-status.txt` | Status of WARP switch (`Connected` or `Disconnected`). |
-| `wdutil-info.txt` | |
-| `xpc-launchd.log` | |
+| `wdutil-info.txt` | Wi-Fi diagnostics (macOS only). |
+| `xpc-launchd.log` | Most recent log file for the `launchd` process on macOS. |
 
 #### Multiple versions of the same log
 

From 17f53e6de22726c5210abdc1123fc04847a70921 Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Fri, 11 Oct 2024 12:11:07 -0400
Subject: [PATCH 08/10] link to fleet status page

---
 .../docs/cloudflare-one/insights/dex/remote-captures.mdx        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
index 135af47855c559..9dbcad7a715905 100644
--- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -56,7 +56,7 @@ To view a list of captures, go to **DEX** > **Remote captures**. The **Status**
 	- **Success**: The capture is complete and ready for download.
 	- **Running**: The capture is in progress on the device.
 	- **Pending Upload**: The capture is complete but not yet ready for download.
-	- **Failed**: The capture has either timed out or encountered an error. To retry the capture, make sure the WARP client is connected and start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture).
+	- **Failed**: The capture has either timed out or encountered an error. To retry the capture, verify the [connectivity status](/cloudflare-one/insights/dex/fleet-status/) of the device and start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture).
 
 ## Download remote captures
 

From fb02b316fc585c2abb39c6a5757d06065a35a02d Mon Sep 17 00:00:00 2001
From: Ranbel Sun <ranbel@cloudflare.com>
Date: Wed, 30 Oct 2024 19:27:05 -0400
Subject: [PATCH 09/10] apply review feedback

---
 .../warp/troubleshooting/warp-logs.mdx        |  6 +--
 .../insights/dex/remote-captures.mdx          | 51 ++++++++++++-------
 2 files changed, 37 insertions(+), 20 deletions(-)

diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
index 0bb873a0e95d38..999793deb35154 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs.mdx
@@ -67,13 +67,13 @@ The `warp-debugging-info-<date>-<time>.zip` archive contains the following files
 | `daemon_dns.log` | Contains detailed DNS logs if **Log DNS queries** is enabled in the WARP client. |
 | `daemon.log`                                                                                        | Detailed log of all actions performed by the WARP client, including all communication between the device and Cloudflare's global network. **Note:** This is the most useful debug log.   |
 | `date.txt`  | Date and time (UTC) when you ran the `warp-diag` command.  |
-| `dex.log`  | ? |
+| `dex.log`  | Logs related to [DEX test](/cloudflare-one/insights/dex/tests/) execution. |
 | `dhcp-lease-plists.txt`  | DHCP lease information from `/var/db/dhcpclient/leases/` for each interface that has a DHCP lease. |
 | `dhcp-lease.txt`  | DHCP lease information from `ipconfig` (macOS) or `nmcli` (Linux). |
 | `dig.txt`  | DNS lookup query output for `cloudflare.com` and `apple.com`. |
 | `dns_stats.log`  | Statistics on the DNS queries received and resolved by WARP, generated every two minutes.  |
 | `dns-check.txt` | Verifies that the WARP DNS servers are set as system default. For [operating modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) where DNS filtering is enabled, this file contains the IPs of the local WARP DNS proxy (`127.0.2.2:0`, `127.0.2.3:0`, `[fd01:db8:1111::2]:0`, and `[fd01:db8:1111::3]:0`). |
-| `dynamic.log` | ? |
+| `dynamic.log` | Reserved for use by Cloudflare Support. |
 | `etc-hosts.txt`  | Static DNS config of device.  |
 | `firewall-pfctl-all.txt` | Packet filter (pf) firewall configuration (macOS only). |
 | `firewall-rules.txt` | The [system firewall rules](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#system-firewall) configured by WARP. |
@@ -81,7 +81,7 @@ The `warp-debugging-info-<date>-<time>.zip` archive contains the following files
 | `gui-log.log`  | Log file for the GUI app that users interact with. |
 | `hostname.txt` | Name of the device.  |
 | `ifconfig.txt` <br/> `ipconfig.txt`  | IP configuration of each network interface.  |
-| `installed_applications.text` | List of installed applications. |
+| `installed_applications.txt` | List of installed applications. |
 | `installed_cert.pem` | [Root certificate](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/) installed on the system. |
 | `installer.log` <br/> `msi-installer.log` | MSI or PKG installation log.|
 | `InstallHistory.plist` <br/> `macos_installer.log` | macOS software installation logs. |
diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
index 9dbcad7a715905..2bc9c3903154dd 100644
--- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -17,9 +17,9 @@ import { Details, Render } from "~/components"
 
 | System   | Availability | Minimum WARP version |
 | -------- | ------------ | -------------------- |
-| Windows  | ✅            | 2024.9.346.0        |
-| macOS    | ✅            | 2024.9.346.0        |
-| Linux    | ✅            | 2024.9.346.0        |
+| Windows  | ✅            | 2024.9.346.0         |
+| macOS    | ✅            | 2024.9.346.0         |
+| Linux    | ✅            | 2024.9.346.0         |
 | iOS      | ❌            |                      |
 | Android  | ❌            |                      |
 | ChromeOS | ❌            |                      |
@@ -28,6 +28,11 @@ import { Details, Render } from "~/components"
 
 Remote captures allow administrators to collect packet captures (PCAPs) and WARP diagnostic logs directly from end user devices. This data can be used to troubleshoot network problems, investigate security incidents, and identify performance bottlenecks.
 
+:::note
+DEX remote captures are available in early access. For more information, contact your account team.
+:::
+
+
 ## Start a remote capture
 
 To capture data from a remote device:
@@ -36,16 +41,10 @@ To capture data from a remote device:
 2. Select up to 10 devices that you want to run a capture on. Devices must be [registered](/cloudflare-one/connections/connect-devices/warp/deployment/) in your Zero Trust organization.
 3. Configure the types of captures to run.
 	- **PCAP**: Performs packet captures for traffic outside of the WARP tunnel (default network interface) and traffic inside of the WARP tunnel ([WARP virtual interface](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic)).
-		<Details header="PCAP capture limits">
-		Packet captures are subject to the following limits:
-			- **Maximum time limit**: 600 seconds
-			- **Maximum file size**: 50 MB
-			- **Maximum packet size**: 1500 bytes
-		</Details>
 	- **WARP Diagnostics Logs**: Generates a [WARP diagnostic log](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) of the past 96 hours. To include a routing test for all IPs and domains in your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/), select **Test all routes**.
-		<Details header="WARP capture limits">
-		WARP diagnostic logs have no file size limit, but files larger than 100 MB cannot be uploaded to Cloudflare and must be shared directly with the admin.
-		</Details>
+	:::note
+	**Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test.
+	:::
 4. Select **Start a capture**.
 
 DEX will now send capture requests to the configured devices. If the WARP client is disconnected, the capture will time out after 10 minutes.
@@ -53,10 +52,10 @@ DEX will now send capture requests to the configured devices. If the WARP client
 ## Check remote capture status
 
 To view a list of captures, go to **DEX** > **Remote captures**. The **Status** column displays one of the following options:
-	- **Success**: The capture is complete and ready for download.
+	- **Success**: The capture is complete and ready for download. Any partially successful captures will still upload to Cloudflare. For example, there could be a scenario where the PCAP succeeds on the primary network interface but fails on the WARP tunnel interface. You can [review PCAP results](/cloudflare-one/insights/dex/remote-captures/#download-remote-captures) to determine which PCAPs succeeded or failed.
 	- **Running**: The capture is in progress on the device.
 	- **Pending Upload**: The capture is complete but not yet ready for download.
-	- **Failed**: The capture has either timed out or encountered an error. To retry the capture, verify the [connectivity status](/cloudflare-one/insights/dex/fleet-status/) of the device and start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture).
+	- **Failed**: The capture has either timed out or encountered an error. To retry the capture, check the WARP client version and [connectivity status](/cloudflare-one/insights/dex/fleet-status/), then start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture).
 
 ## Download remote captures
 
@@ -64,8 +63,26 @@ To view a list of captures, go to **DEX** > **Remote captures**. The **Status**
 2. Find a successful capture.
 3. Select the three-dot menu and select **Download**.
 
-This will download a ZIP file to your local machine. You can analyze `.pcap` files using Wireshark or another third-party packet capture tool.
+This will download a ZIP file to your local machine called `<capture-id>.zip`. DEX will store capture data according to our [log retention policy](/cloudflare-one/insights/logs/#log-retention).
+
+### Device PCAP contents
+
+The downloaded PCAP folder contains three files:
+- `capture-default.pcap`: Packet captures for the primary network interface.
+- `capture-tunnel.pcap`: Packet captures for traffic inside of the WARP tunnel.
+- `results.json`: Reports successful and failed packet captures.
+
+You can analyze `.pcap` files using Wireshark or another third-party packet capture tool.
+
+### WARP Diag contents
+
+Refer to [WARP diagnostic logs](/cloudflare-one/connections/connect-devices/warp/troubleshooting/warp-logs/#warp-diag-logs) for a description of each file.
 
-## Data retention
+## Limitations
 
-Cloudflare will store capture data for 7 days.
\ No newline at end of file
+- Packet captures are subject to the following limits:
+	- **Maximum time limit**: 600 seconds
+	- **Maximum file size**: 50 MB
+	- **Maximum packet size**: 1500 bytes
+- WARP diagnostic logs have no file size limit, but files larger than 100 MB cannot be uploaded to Cloudflare and must be shared directly with the admin.
+- Windows devices do not support concurrent remote captures. If you start a remote capture while another is in progress, the second capture will fail immediately.

From 17fe0c71b457cc95847d57560e7cda189074738f Mon Sep 17 00:00:00 2001
From: Claire Waters <cwaters@cloudflare.com>
Date: Tue, 5 Nov 2024 16:20:57 -0600
Subject: [PATCH 10/10] updating availability matrix

---
 .../insights/dex/remote-captures.mdx          | 25 ++-----------------
 1 file changed, 2 insertions(+), 23 deletions(-)

diff --git a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
index 2bc9c3903154dd..a1e66e2d128a54 100644
--- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
+++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx
@@ -6,32 +6,11 @@ sidebar:
 
 ---
 
-import { Details, Render } from "~/components"
-
-
-<Details header="Feature availability">
-
-| [WARP modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) | [Zero Trust plans](https://www.cloudflare.com/teams-pricing/) |
-| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
-| All modes                                                                                 | All plans                                                     |
-
-| System   | Availability | Minimum WARP version |
-| -------- | ------------ | -------------------- |
-| Windows  | ✅            | 2024.9.346.0         |
-| macOS    | ✅            | 2024.9.346.0         |
-| Linux    | ✅            | 2024.9.346.0         |
-| iOS      | ❌            |                      |
-| Android  | ❌            |                      |
-| ChromeOS | ❌            |                      |
-
-</Details>
-
-Remote captures allow administrators to collect packet captures (PCAPs) and WARP diagnostic logs directly from end user devices. This data can be used to troubleshoot network problems, investigate security incidents, and identify performance bottlenecks.
-
 :::note
-DEX remote captures are available in early access. For more information, contact your account team.
+DEX remote captures are available for beta testing on [Windows](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows/distribution_groups/beta) and [macOS](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos/distribution_groups/beta). Linux builds are available upon request by contacting your account team.
 :::
 
+Remote captures allow administrators to collect packet captures (PCAPs) and WARP diagnostic logs directly from end user devices. This data can be used to troubleshoot network problems, investigate security incidents, and identify performance bottlenecks.
 
 ## Start a remote capture