From f0d2b9fcfa8732f13dca0632cd8044c38c884d5a Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Wed, 29 Jan 2025 15:44:16 +0000 Subject: [PATCH 1/3] [CF1] device monitoring --- public/_redirects | 1 + .../insights/dex/fleet-status.mdx | 41 ---------- .../insights/dex/ip-visibility.mdx | 4 +- .../insights/dex/monitoring.mdx | 80 +++++++++++++++++++ .../insights/dex/remote-captures.mdx | 37 ++++----- .../insights/dex/tests/index.mdx | 5 +- 6 files changed, 102 insertions(+), 66 deletions(-) delete mode 100644 src/content/docs/cloudflare-one/insights/dex/fleet-status.mdx create mode 100644 src/content/docs/cloudflare-one/insights/dex/monitoring.mdx diff --git a/public/_redirects b/public/_redirects index 78128813685b758..24abca2b89eab96 100644 --- a/public/_redirects +++ b/public/_redirects @@ -1845,6 +1845,7 @@ /cloudflare-one/policies/browser-isolation/agentless/* /cloudflare-one/policies/browser-isolation/setup/:splat 301 /cloudflare-one/policies/filtering/http-policies/data-loss-prevention/* /cloudflare-one/policies/data-loss-prevention/ 301 /cloudflare-one/policies/data-loss-prevention/configuration-guides/* /cloudflare-one/policies/data-loss-prevention/dlp-policies/common-policies/ 301 +/cloudflare-one/insights/dex/fleet-status/ /cloudflare-one/insights/dex/monitoring/ 301 # Learning paths /learning-paths/modules/cybersafe/cybersafe-account-creation/* /learning-paths/cybersafe/account-creation/:splat 301 diff --git a/src/content/docs/cloudflare-one/insights/dex/fleet-status.mdx b/src/content/docs/cloudflare-one/insights/dex/fleet-status.mdx deleted file mode 100644 index 6b77dba0497935f..000000000000000 --- a/src/content/docs/cloudflare-one/insights/dex/fleet-status.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -pcx_content_type: reference -title: Fleet status -sidebar: - order: 1 - ---- - -With DEX, you can monitor your users' devices and connection status. - -## View metrics - -To view an overview of all enrolled devices, go to **DEX** > **Monitoring**. The **Fleet Status** tab will show real-time and historical connectivity metrics for all devices in your organization. - -To view analytics on a per-device level, go to **My Team** > **Devices**. The **Fleet Status** tab will show real-time and historical connectivity metrics for the selected device. - -## Available metrics - -* **Devices connected by colo**: Number of devices that are connected to a given [Cloudflare data center](https://www.cloudflarestatus.com/). - -* **Connectivity status**: Percentage of devices in a given WARP client state. - - | Status | Description | - |-------------------|-------------| - | Connected | WARP has successfully established a connection to the Cloudflare global network. | - | Disconnected | WARP has been intentionally or unintentionally disconnected from the Cloudflare global network. | - | Paused | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [Admin Override](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#admin-override) code. Paused clients will [auto-connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect) after a timeout period. | - | Connecting | WARP is pending connection, but is actively trying to establish a connection to the Cloudflare global network. | - - -* **Mode**: [WARP mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) deployed on the device. - -* **Colo**: Percentage of devices connected to a given Cloudflare data center. - -* **Platform**: Operating system of the device. - -* **Major Version**: WARP client version installed on the device. - -* **Device Status Over Time**: WARP client connection status over the selected time period. - -* **Connection Methods Over Time**: WARP mode used by the device over the selected time period. diff --git a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx index 7c2511c7ba6bb8b..2eae8433dbed44b 100644 --- a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx @@ -48,11 +48,11 @@ DEX's IP visibility allows you to review an event log of a device's IP history f 4. View the device's IP history and status from the last seven days. 5. Select a time to view more information about the device at that time. -Refer to [Available metrics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) to review **Status** and **Mode** descriptions. +Refer to [Available metrics](/cloudflare-one/insights/dex/monitoring/#available-metrics) to review **Status** and **Mode** descriptions. ## Troubleshoot with IP visbility -While IP visibility allows you to inspect a device's IP information, use [DEX's live analytics](/cloudflare-one/insights/dex/fleet-status/#available-metrics) to review which Cloudflare data center the device is connected to. When traffic leaves a WARP-connected end-user device, it will hit a [Cloudflare data center](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request). +While IP visibility allows you to inspect a device's IP information, use [DEX's live analytics](/cloudflare-one/insights/dex/monitoring/#available-metrics) to review which Cloudflare data center the device is connected to. When traffic leaves a WARP-connected end-user device, it will hit a [Cloudflare data center](/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#identify-the-cloudflare-data-center-serving-your-request). To find which Cloudflare data center a device is connected to: diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx new file mode 100644 index 000000000000000..ef353b0be365297 --- /dev/null +++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx @@ -0,0 +1,80 @@ +--- +pcx_content_type: reference +title: Monitoring +sidebar: + order: 1 +--- + +Monitor performance and network status for your organization's [fleet](/cloudflare-one/insights/dex/monitoring/#fleet-status) or individual [user devices](/cloudflare-one/insights/dex/monitoring/#device-monitoring). + +Network and device performance data helps IT administrators troubleshoot performance issues, investigate network connectivity problems, and monitor device health. + +## Fleet status + +A fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Cloudflare Zero Trust organization](/cloudflare-one/setup/#create-a-zero-trust-organization). + +To view fleet status: + +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Monitoring**. +2. In **DEX Monitoring**, review the information under the **Fleet Status** tab. + +### View metrics + +The **Fleet Status** tab will show real-time and historical connectivity metrics for all devices in your organization. + +To view analytics on a per-device level, go to [Device monitoring](/cloudflare-one/insights/dex/monitoring/#device-monitoring). + +### Available metrics + +- **Devices connected by colo**: Number of devices that are connected to a given [Cloudflare data center](https://www.cloudflarestatus.com/). + +- **Connectivity status**: Percentage of devices in a given WARP client state. + + | Status | Description | + | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | + | Connected | WARP has successfully established a connection to the Cloudflare global network. | + | Disconnected | WARP has been intentionally or unintentionally disconnected from the Cloudflare global network. | + | Paused | A user or administrator has taken an explicit action to temporarily turn off WARP, for example by entering an [Admin Override](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#admin-override) code. Paused clients will [auto-connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect) after a timeout period. | + | Connecting | WARP is pending connection, but is actively trying to establish a connection to the Cloudflare global network. | + +- **Mode**: [WARP mode](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) deployed on the device. + +- **Colo**: Percentage of devices connected to a given Cloudflare data center. + +- **Platform**: Operating system of the device. + +- **Major Version**: WARP client version installed on the device. + +- **Device Status Over Time**: WARP client connection status over the selected time period. + +- **Connection Methods Over Time**: WARP mode used by the device over the selected time period. + +## Device monitoring + +Review network and device performance for a device enrolled in your fleet. + +### View a device's performance + +To view a device's network and device performance metrics: + +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. +2. Select a device > **View details**. +3. Select the **DEX** tab > in **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. + +### Network and device performance metrics + +#### Network performance metrics + +- **Unique networks over time**: How many unique SSIDs the device was connected to. + +- **Network I/O**: How much data has been transferred (uploads and downloads) over the primary network interface. + +#### Device performance metrics + +- **Battery percentage and cycles**: Displays battery percentage and [battery cycles](https://support.apple.com/en-us/102888) over time. Used to debug potential performance issues possibly related to battery health or power-saving measures that are triggered at low-battery levels. + +- **CPU usage**: CPU utilization over time. Used to debug slow system performance due to high CPU usage. + +- **Memory utilization**: Memory utilization over time. Used to debug performance issues related to an overtaxed memory. + +- **Disk I/O**: Displays number of disk read/write operations over time. Used to debug performance errors due to heavy disk operations. 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 040942d663be95d..76195391cb8ad54 100644 --- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx @@ -5,7 +5,7 @@ sidebar: order: 4 --- -import { Details } from "~/components" +import { Details } from "~/components";
@@ -15,12 +15,12 @@ import { Details } from "~/components" | System | Availability | Minimum WARP version | | -------- | ------------ | -------------------- | -| Windows | ✅ | 2024.12.492.0 | -| macOS | ✅ | 2024.12.492.0 | -| Linux | ✅ | 2024.12.492.0 | -| iOS | ❌ | | -| Android | ❌ | | -| ChromeOS | ❌ | | +| Windows | ✅ | 2024.12.492.0 | +| macOS | ✅ | 2024.12.492.0 | +| Linux | ✅ | 2024.12.492.0 | +| iOS | ❌ | | +| Android | ❌ | | +| ChromeOS | ❌ | |
@@ -33,22 +33,18 @@ To capture data from a remote device: 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. 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)). - - **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**. - :::note - **Test all routes** will extend the time for diagnostics to run and may temporarily impact device performance during the test. - ::: + - **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)). + - **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**. + :::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. ## 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. 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, 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). +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. 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, check the WARP client version and [connectivity status](/cloudflare-one/insights/dex/monitoring/#fleet-status), then start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture). ## Download remote captures @@ -61,6 +57,7 @@ This will download a ZIP file to your local machine called `.zip`. D ### 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. @@ -74,8 +71,8 @@ Refer to [WARP diagnostic logs](/cloudflare-one/connections/connect-devices/warp ## Limitations - Packet captures are subject to the following limits: - - **Maximum time limit**: 600 seconds - - **Maximum file size**: 50 MB - - **Maximum packet size**: 1500 bytes + - **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. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx index 49df86137f2e054..704c964e5e16538 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/index.mdx @@ -3,11 +3,10 @@ pcx_content_type: navigation title: Tests sidebar: order: 2 - --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; -With Digital Experience Monitoring (DEX), you can test if your devices can connect to a private or public endpoint through the WARP client. This tool allows you to monitor availability for a given application and investigate performance issues reported by your end users. DEX tests will only run when the WARP client is turned on, whereas [fleet status](/cloudflare-one/insights/dex/fleet-status/) metrics are always available. +With Digital Experience Monitoring (DEX), you can test if your devices can connect to a private or public endpoint through the WARP client. This tool allows you to monitor availability for a given application and investigate performance issues reported by your end users. DEX tests will only run when the WARP client is turned on, whereas [fleet status](/cloudflare-one/insights/dex/monitoring/#fleet-status) metrics are always available. From a28df58ea39278ae0085799ca770c8bbca39b919 Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Wed, 29 Jan 2025 15:47:45 +0000 Subject: [PATCH 2/3] Update src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx --- .../docs/cloudflare-one/insights/dex/remote-captures.mdx | 6 +++++- 1 file changed, 5 insertions(+), 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 76195391cb8ad54..ecb5c9dbdd0e404 100644 --- a/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/remote-captures.mdx @@ -44,7 +44,11 @@ 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. 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, check the WARP client version and [connectivity status](/cloudflare-one/insights/dex/monitoring/#fleet-status), then start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture). +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. 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, check the WARP client version and [connectivity status](/cloudflare-one/insights/dex/monitoring/#fleet-status), then start a [new capture](/cloudflare-one/insights/dex/remote-captures/#start-a-remote-capture). ## Download remote captures From b6e1bc68210b31b665183e7c34463da6f3f8b81c Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Fri, 21 Feb 2025 10:55:51 +0000 Subject: [PATCH 3/3] Update src/content/docs/cloudflare-one/insights/dex/monitoring.mdx --- src/content/docs/cloudflare-one/insights/dex/monitoring.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx index ef353b0be365297..a111edc828507c2 100644 --- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx @@ -59,7 +59,8 @@ To view a device's network and device performance metrics: 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. 2. Select a device > **View details**. -3. Select the **DEX** tab > in **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. +3. Select the **DEX** tab. +4. In **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. ### Network and device performance metrics