-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[DEX] device monitoring #19388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DEX] device monitoring #19388
Conversation
|
This PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:
|
Deploying cloudflare-docs with
|
| Latest commit: |
26c5b59
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2859b3b5.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://kate-fixes-endpointmanagemen.cloudflare-docs-7ou.pages.dev |
|
|
||
| - **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) between the device and the network. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we say something like "How much data has been transferred (uploads and downloads) over the primary network interface."?
|
|
||
| #### Device performance metrics | ||
|
|
||
| - **Battery percentage and cycles**: Compares battery percentage to battery health over time. Used to debug potential performance issues possibly related to power-saving measures that are triggered at low-battery levels. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should say "Displays" instead of "Compares" here
|
|
||
| - **Memory utilization**: Memory utilization over time. Used to debug performance issues related to an overtaxed memory. | ||
|
|
||
| - **Disk I/O**: Displays number of disk bytes read/write operations over time. Used to debug performance errors due to heavy disk operations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove the word "bytes" here - the UI will dynamically choose units to show based on size
| - **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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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). |
Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
* Update settings.mdx elaboration on resolved host cache key setting * Update src/content/docs/cache/how-to/cache-rules/settings.mdx --------- Co-authored-by: angelampcosta <[email protected]>
Co-authored-by: Pedro Sousa <[email protected]>
Summary
13859
Documentation checklist