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 cc31272d8b4293..72ec3d3a8cd3ca 100644 --- a/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/ip-visibility.mdx @@ -46,17 +46,16 @@ IP information is crucial for IT administrators to accurately troubleshoot netwo To view IP information for a user device: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. -2. Select a device, then select **View details**. -3. Under **Details**, scroll down to **IP details**. -4. Review the IP details for your selected device's most recent session. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +2. Select a device, then select **View details** > **IP**. +3. Under **IP details**, review the IP details for your selected device's most recent session. ## View a device's IP history DEX's IP visibility allows you to review an event log of a device's IP history for the last seven days. To view a device's IP history: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. -2. Select a device > **View details** > under **Details**, scroll down to **IP details**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +2. Select a device > **View details** > select **IP** > under **IP details**, review IP details from this device's most recent session. 3. Select **View device history**. 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. @@ -69,6 +68,6 @@ While IP visibility allows you to inspect a device's IP information, use [DEX's To find which Cloudflare data center a device is connected to: -1. Follow the steps listed in [View IP information](#view-a-devices-ip-history) to find a device's IP information. -2. Select **Device Monitoring** above **Device event log**. -3. Find **Colo** in the **Device details** table to review which Cloudflare data center your selected device's egress traffic is connected to. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +2. Select a device, then select **View details**. +3. Under **Client**, review the **Colocation** details to review which Cloudflare data center your selected device's egress traffic 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 index 0fb541bc64b100..a419788c4bf969 100644 --- a/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/monitoring.mdx @@ -9,18 +9,18 @@ Monitor performance and network status for your organization's [fleet](/cloudfla Network and device performance data helps IT administrators troubleshoot performance issues, investigate network connectivity problems, and monitor device health. -## Fleet status +## Device overview -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). +A fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [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. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience**. +2. In **Device overview**, review the information under the **Live analytics** tab. ### View metrics -The **Fleet Status** tab will show real-time and historical connectivity metrics for all devices in your organization. +The **Device overview** 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). @@ -39,15 +39,15 @@ To view analytics on a per-device level, go to [Device monitoring](/cloudflare-o - **Mode**: [WARP mode](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-modes/) deployed on the device. -- **Colo**: Percentage of devices connected to a given Cloudflare data center. +- **Colocation**: 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. +- **Major version**: WARP client version installed on the device. -- **Device Status Over Time**: WARP client connection status over the selected time period. +- **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. +- **Connection methods over time**: WARP mode used by the device over the selected time period. ## Device monitoring @@ -57,10 +57,10 @@ Review network and device performance for a device enrolled in your fleet. To view a device's network and device performance metrics: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My team** > **Devices**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. 2. Select a device > **View details**. -3. Select the **DEX** tab. -4. In **Device Monitoring**, scroll down to **Network performance** and **Device Performance**. +3. Select the **Monitoring** tab. +4. Scroll down to **Network performance** and **Device Performance**. ### Network and device performance metrics diff --git a/src/content/docs/cloudflare-one/insights/dex/rules.mdx b/src/content/docs/cloudflare-one/insights/dex/rules.mdx index ed283403536285..1e9d5e8bbd35d8 100644 --- a/src/content/docs/cloudflare-one/insights/dex/rules.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/rules.mdx @@ -15,7 +15,7 @@ DEX rules are ideal for admins who want to define the scope of a test to a speci To create a rule: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Rules**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Rules**. 2. Select **Add a rule**. 3. Give your rule a name and build your desired expressions. 4. Select **Create rule** to finalize your rule. @@ -44,7 +44,7 @@ After you have created a rule, you can add it to a test. If you do not add a rul To add a rule to a test: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Tests**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Tests**. 2. Choose an existing test and select **Edit**, or select **Add a test** to make a new test. 3. Under **Select DEX rules**, select the rule you would like to apply. 4. Select **Save test** for an existing rule or **Add rule** for the new test. @@ -55,7 +55,7 @@ To add a rule to a test: To view which tests a rule is being applied to: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Rules**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Rules**. 2. Select a rule > **Edit**. 3. Select the **DEX tests** tab and review the list of tests that include your selected rule. @@ -65,10 +65,10 @@ You can create a new test from the [DEX test dashboard as described above](/clou To create a new test using a rule from DEX rules: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Rules**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Rules**. 2. Select a rule > **Edit**. 3. Select the **DEX tests** tab. -4. You will be able to review all the tests that currently include this rule. To create a new test, select **Create a test using this rule**. +4. You will be able to review all the tests that currently include this rule. To create a new test, select **Create a test for rule**. 5. Enter all required information, making sure that the box next to your rule name is checked. 6. Select **Add test**. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/http.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/http.mdx index 7ea377d6c7d907..2ed24938d0ee22 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/http.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/http.mdx @@ -30,7 +30,7 @@ An HTTP test sends a `GET` request from an end-user device to a specific web app To set up an HTTP test for an application: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Tests**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Tests**. 2. Select **Add a Test**. 3. Fill in the following fields: - **Name**: Enter any name for the test. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx index 15cc294c016b21..6784a6209f8e67 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx @@ -30,7 +30,7 @@ A traceroute test measures the network path of an IP packet from an end-user dev To set up a traceroute test for an application: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Tests**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Tests**. 2. Select **Add a Test**. 3. Fill in the following fields: - **Name**: Enter any name for the test. diff --git a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx index 2193c3581ff5fb..90428237187012 100644 --- a/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx +++ b/src/content/docs/cloudflare-one/insights/dex/tests/view-results.mdx @@ -16,17 +16,17 @@ Use the results of a DEX test to monitor availability and performance for a spec To view an overview of test results for all devices: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Monitoring**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Tests**. 2. Select the **Tests** tab. -3. Under **Application tests**, select a test to view detailed results. +3. Select a test to view detailed results. ## View results for an individual device To view analytics on a per-device level: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **My Team** > **Devices**. -2. Select the device you want to view, and then select **View details**. -3. Select the **Tests** tab. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Teams & Resources** > **Devices**. +2. Select the device you want to view > select **View details**. +3. Select the **Synthetic tests** tab. 4. Select a test to view detailed results. ## Related resources diff --git a/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx index 56f39f4e33ca14..a3de4dc2f79077 100644 --- a/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx @@ -1,6 +1,6 @@ --- pcx_content_type: reference -title: Access audit logs +title: Access authentication logs sidebar: order: 2 head: [] @@ -35,7 +35,7 @@ Authentication logs do not capture the user's actions during a self-hosted or Sa To view logs for identity-based authentication events: -1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Logs** > **Access**. +1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Logs** > **Access**. 2. Select a row to view details such as the login method, the IP address of the user, and more. diff --git a/src/content/docs/cloudflare-one/insights/logs/gateway-logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/gateway-logs/index.mdx index 08bc7051fdd2bd..9044dd56e927c4 100644 --- a/src/content/docs/cloudflare-one/insights/logs/gateway-logs/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/gateway-logs/index.mdx @@ -1,6 +1,6 @@ --- pcx_content_type: reference -title: Gateway activity logs +title: Gateway activity logs (DNS query, HTTP request, Network logs) sidebar: order: 3 --- @@ -15,15 +15,25 @@ Gateway logs will only show the public IP address for the **Source IP** field. P Gateway activity logs show the individual DNS queries, Network packets, and HTTP requests inspected by Gateway. You can also download encrypted [SSH command logs](/cloudflare-one/traffic-policies/network-policies/ssh-logging/) for sessions proxied by Gateway. -To view Gateway activity logs, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Logs** > **Gateway**. Select an individual row to investigate the event in more detail. +To view Gateway activity logs: + +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights**. +2. Go to **Logs** and select the Gateway logs you are interested in reviewing (DNS queries, Network packets, or HTTP requests.) +3. Select an individual row to investigate the event in more detail. Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/insights/logs/logpush/). ## Selective logging -By default, Gateway logs all events, including DNS queries and HTTP requests that are allowed and not a risk. You can choose to disable logs or only log blocked requests. To customize what type of events are recorded, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Settings** > **Network**. Under **Activity Logging**, indicate your DNS, Network, and HTTP log preferences. +By default, Gateway logs all events, including DNS queries and HTTP requests that are allowed and not a risk. You can choose to disable logs or only log blocked requests. + +To customize what type of events are recorded: + +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies**. +2. Go to **Traffic settings**. +3. Select **Traffic logging**, and indicate your Gateway DNS, Network, and HTTP log preferences. -These settings will only apply to logs displayed in Zero Trust. Logpush data is unaffected. +These settings will only apply to logs displayed in Cloudflare One. Logpush data is unaffected. ## DNS logs @@ -62,7 +72,7 @@ These settings will only apply to logs displayed in Zero Trust. Logpush data is | **Registration ID** | UUID of the user's WARP client registration. A unique registration ID is generated each time a device is registered for a particular email. The same physical device may have multiple registration IDs. | | **Device name** | Display name of the device returned by the operating system to the WARP client. Typically this is the hostname of a device. Not all devices will have a device name. Device names are not guaranteed to be unique. | | **Device ID** | UUID of the device connected with the WARP client. Each physical device in your organization will have a UUID. | -| **Last authenticated** | Date and time the user last authenticated their Zero Trust session. | +| **Last authenticated** | Date and time the user last authenticated their session. | #### DNS query details @@ -159,7 +169,7 @@ Gateway can log failed connections in [network session logs](/logs/logpush/logpu | **Registration ID** | ID of the user's device registration. This is generated by the WARP client. | | **Device name** | Name of the device that sent the packet. | | **Device ID** | ID of the physical device that sent the packet. This is generated by the WARP client. | -| **Last authenticated** | Date and time the user last authenticated with Zero Trust. | +| **Last authenticated** | Date and time the user last authenticated with Cloudflare One. | #### Network query details @@ -229,7 +239,7 @@ When an HTTP request results in an error, Gateway logs the first 512 bytes of th | **Registration ID** | ID of the user's device registration. This is generated by the WARP client. | | **Device name** | Name of the device that made the request. | | **Device ID** | ID of the physical device that made the request. This is generated by the WARP client on the device that created the request. | -| **Last authenticated** | Date and time the user last authenticated with Zero Trust. | +| **Last authenticated** | Date and time the user last authenticated with Cloudflare One. | #### HTTP query details @@ -275,13 +285,13 @@ Enhanced file detection is an optional feature to extract more file information To turn on enhanced file detection: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Network**. -2. In **Firewall**, turn on **TLS decryption**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies** > **Traffic settings**. +2. In **Proxy and inspection**, turn on **Inspect HTTPS requests with TLS decryption**. 3. In **Gateway Logging**, turn on **Enable enhanced file detection**. ### Isolate requests -When a user creates an [isolation policy](/cloudflare-one/remote-browser-isolation/isolation-policies/), Gateway logs the initial request that triggers isolation as an Isolate action. Because this request is not isolated yet, the `is_isolated` field will return `false`. Zero Trust then securely returns the result to the user in an isolated browser. Gateway will log all subsequent requests in the isolated browser with the action (such as Allow or Block), and the `is_isolated` field will return `true`. +When a user creates an [isolation policy](/cloudflare-one/remote-browser-isolation/isolation-policies/), Gateway logs the initial request that triggers isolation as an Isolate action. Because this request is not isolated yet, the `is_isolated` field will return `false`. Cloudflare One then securely returns the result to the user in an isolated browser. Gateway will log all subsequent requests in the isolated browser with the action (such as Allow or Block), and the `is_isolated` field will return `true`. ## Limitations diff --git a/src/content/docs/cloudflare-one/insights/logs/gateway-logs/manage-pii.mdx b/src/content/docs/cloudflare-one/insights/logs/gateway-logs/manage-pii.mdx index aa29f4734643b8..5dddab532a5ab8 100644 --- a/src/content/docs/cloudflare-one/insights/logs/gateway-logs/manage-pii.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/gateway-logs/manage-pii.mdx @@ -23,7 +23,11 @@ Cloudflare Gateway can log the following types of PII: Enabling this setting means Cloudflare Gateway will log activity without storing any employee PII. Changes to this setting will not change PII storage of any previous logs. This means if Exclude PII is enabled and then disabled, there will be no PII data for logs captured while Exclude PII was enabled. The PII data will be unavailable to all roles within your Zero Trust organization, including the Super Admin. -To enable or disable this setting, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Traffic policies** > **Traffic settings** > **Exclude personally identifiable information (PII) from logs**. +To enable or disable this setting: + +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Traffic policies**. +2. Go to **Traffic settings**. +2. Toggle **Exclude personally identifiable information (PII) from logs** to your desired state. ## Redact PII diff --git a/src/content/docs/cloudflare-one/insights/logs/index.mdx b/src/content/docs/cloudflare-one/insights/logs/index.mdx index 1386a68cee7957..2075718d4cdf86 100644 --- a/src/content/docs/cloudflare-one/insights/logs/index.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/index.mdx @@ -40,8 +40,8 @@ For more information, refer to [Log Explorer](/log-explorer/). ## Customer Metadata Boundary -Cloudflare Zero Trust can be used with the Data Localization Suite to ensure that data storage is restricted to a specific geographic region. For more information refer to [Customer Metadata Boundary](/data-localization/metadata-boundary/). +Cloudflare Zero Trust can be used with the Data Localization Suite to ensure that data storage is restricted to a specific geographic region. For more information, refer to [Customer Metadata Boundary](/data-localization/metadata-boundary/). ## Data privacy -For more information on how we use this data, refer to our [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/). +For more information on how we use this data, refer to Cloudflare's [Privacy Policy](https://www.cloudflare.com/application/privacypolicy/). diff --git a/src/content/docs/cloudflare-one/insights/logs/logpush.mdx b/src/content/docs/cloudflare-one/insights/logs/logpush.mdx index b4ee35fbe89de7..7b032f03d4681c 100644 --- a/src/content/docs/cloudflare-one/insights/logs/logpush.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/logpush.mdx @@ -21,9 +21,9 @@ Zero Trust does not support configuring [Cloudflare R2](/logs/logpush/logpush-jo To configure Logpush for Zero Trust logs: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Logs** > **Logpush**. -2. If this is your first Logpush job, select **Add a Logpush job**. Otherwise, select **Go to logpush configurations**. -3. In Logpush, select **Create a Logpush job**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights**. +2. Select **Manage Logpush**. +3. Select **Create a Logpush job**. 4. Choose a [Logpush destination](/logs/logpush/logpush-job/enable-destinations/). 5. Follow the service-specific instructions to configure and validate your destination. 6. Choose the [Zero Trust datasets](#zero-trust-datasets) to export. diff --git a/src/content/docs/cloudflare-one/insights/logs/posture-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/posture-logs.mdx index c6bf81eb36270d..9ebd188b06d86c 100644 --- a/src/content/docs/cloudflare-one/insights/logs/posture-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/posture-logs.mdx @@ -8,7 +8,13 @@ sidebar: Posture logs show the [device posture check](/cloudflare-one/reusable-components/posture-checks/) results reported by the WARP client. -To view device posture logs, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Logs** > **Posture**. Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. +To view device posture logs: + +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights**. +2. Go to **Logs**. +3. Select **Posture logs**. + +Logs will only display if you have configured [device posture checks](/cloudflare-one/reusable-components/posture-checks/) for your Zero Trust organization. Enterprise users can generate more detailed logs with [Logpush](/cloudflare-one/insights/logs/logpush/). diff --git a/src/content/docs/cloudflare-one/insights/logs/scim-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/scim-logs.mdx index 6ca0076f787fe5..594fe40e8fa8b2 100644 --- a/src/content/docs/cloudflare-one/insights/logs/scim-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/scim-logs.mdx @@ -8,11 +8,17 @@ sidebar: import { Render } from "~/components"; -SCIM activity logs allow administrators to audit how [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/) events in an identity provider (such as create, update, and delete) affect a user's identity and group membership in Zero Trust. You can compare your Zero Trust SCIM logs with your identity provider's SCIM logs to track how identity data is shared between the two services and pinpoint the source of any provisioning errors. +SCIM activity logs allow administrators to audit how [SCIM provisioning](/cloudflare-one/team-and-resources/users/scim/) events in an identity provider (such as create, update, and delete) affect a user's identity and group membership in Cloudflare One. You can compare your Cloudflare One SCIM logs with your identity provider's SCIM logs to track how identity data is shared between the two services and pinpoint the source of any provisioning errors. ## View SCIM logs -For an overview of SCIM events across all users, log in to [Zero Trust](https://one.dash.cloudflare.com/) and go to **Logs** > **SCIM provisioning**. This page lists the inbound SCIM requests from all identity providers configured with SCIM. You can select an individual request to view more details about the SCIM operation. +For an overview of SCIM events across all users: + +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights**. +2. Go to **Logs**. +3. Select **SCIM provisioning**. + +This page lists the inbound SCIM requests from all identity providers configured with SCIM. You can select an individual request to view more details about the SCIM operation. To investigate how SCIM events impacted a specific user, go to their [User Registry identity](/cloudflare-one/team-and-resources/users/users/). diff --git a/src/content/docs/cloudflare-one/insights/logs/tunnel-audit-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/tunnel-audit-logs.mdx index 4e449e54ed2613..9ab07fb6dd2d2e 100644 --- a/src/content/docs/cloudflare-one/insights/logs/tunnel-audit-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/tunnel-audit-logs.mdx @@ -6,7 +6,13 @@ sidebar: --- -Audit logs for Tunnel are available in the [account section of the Cloudflare dashboard](https://dash.cloudflare.com/?account=audit-log) which you can find by selecting your name or email in the upper right-hand corner of the dashboard. The following actions are logged: +import { DashButton } from "~/components"; + +Audit logs for Tunnel are available in the **Manage account** section of the Cloudflare dashboard. + + + +The following actions are logged: | Action | Description | | ------------ | --------------------------------------------------------------------------------------------------- | diff --git a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx index 1dc1b862e6683b..a7910e83a57a5a 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-download.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-download.mdx @@ -2,7 +2,7 @@ {} --- -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Diagnostics**. 2. Find a successful capture. 3. Select the three-dot menu and select **Download**. diff --git a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx index 12eba4979029a0..1a0ee08ace0c59 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-run.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-run.mdx @@ -8,9 +8,10 @@ Devices must be actively connected to the Internet for remote captures to run. 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/team-and-resources/devices/warp/deployment/) in your Zero Trust organization. -3. Configure the types of captures to run. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Diagnostics**. +2. Select **Run diagnostics**. +3. Select up to 10 devices that you want to run a capture on. Devices must be [registered](/cloudflare-one/team-and-resources/devices/warp/deployment/) in your Cloudflare One organization. +4. Configure the types of captures to run. - **Packet captures (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/team-and-resources/devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic)). - **WARP Diagnostics Logs**: Generates a [WARP diagnostic log](/cloudflare-one/team-and-resources/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/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/), select **Test all routes**. :::note diff --git a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx index bb4c793b9e586d..485c2ca1928e7f 100644 --- a/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx +++ b/src/content/partials/cloudflare-one/dex/pcaps-view-warp-diag.mdx @@ -8,7 +8,7 @@ The WARP diagnostics analyzer highlights what Cloudflare determines to be the mo To access the WARP diagnostic analyzer: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DEX** > **Remote captures**. +1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Insights** > **Digital experience** > **Diagnostics**. 2. Locate an existing `warp-diag` log from the list or select **Run diagnostics** to generate a new `warp-diag` log. 3. Select the three dots for the `warp-diag` log that you want to analyze, then select **View WARP Diag**.