[Logs] Updates logpush navigation with dashbutton (#25757)

* Updates logpush navigation

* Adds more info to path

Author: angelampcosta

src/content/docs/automatic-platform-optimization/get-started/activate-cf-wp-plugin.mdx

@@ -35,7 +35,7 @@ The Cloudflare APO WordPress plugin does not support multisite WordPress install
 
 ## Purchase APO
 
-1. In the Cloudflare dashboard, go to the **Settings** page.
+1. In the Cloudflare dashboard, go to the **Speed** > **Settings** page.
 
    <DashButton url="/?to=/:account/:zone/speed/optimization" />
 

src/content/docs/cache/advanced-configuration/early-hints.mdx

@@ -26,7 +26,7 @@ For more information about Early Hints, refer to the [Cloudflare](https://blog.c
 
 ## Enable Early Hints
 
-1. In the Cloudflare dashboard, go to the **Settings** page.
+1. In the Cloudflare dashboard, go to the **Speed** > **Settings** page.
 
    <DashButton url="/?to=/:account/:zone/speed/optimization" />
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/aws-s3.mdx

@@ -16,9 +16,9 @@ Cloudflare Logpush supports pushing logs directly to Amazon S3 via the Cloudflar
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **Amazon S3**.
+4. In **Select a destination**, choose **Amazon S3**.
 
-6. Enter or select the following destination information:
+5. Enter or select the following destination information:
    - **Bucket** - S3 bucket name
    - **Path** - bucket location within the storage container
    - **Organize logs into daily subfolders** (recommended)
@@ -29,21 +29,21 @@ Cloudflare Logpush supports pushing logs directly to Amazon S3 via the Cloudflar
 
 When you are done entering the destination details, select **Continue**.
 
-7. To prove ownership, Cloudflare will send a file to your designated destination. To find the token, select the **Open** button in the **Overview** tab of the ownership challenge file, then paste it into the Cloudflare dashboard to verify your access to the bucket. Enter the **Ownership Token** and select **Continue**.
+6. To prove ownership, Cloudflare will send a file to your designated destination. To find the token, select the **Open** button in the **Overview** tab of the ownership challenge file, then paste it into the Cloudflare dashboard to verify your access to the bucket. Enter the **Ownership Token** and select **Continue**.
 
-8. Select the dataset to push to the storage service.
+7. Select the dataset to push to the storage service.
 
-9. In the next step, you need to configure your logpush job:
+8. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-10. In **Advanced Options**, you can:
+9. In **Advanced Options**, you can:
     - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
     - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
     - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-11. Select **Submit** once you are done configuring your logpush job.
+10. Select **Submit** once you are done configuring your logpush job.
 
 ## Create and get access to an S3 bucket
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/azure.mdx

@@ -16,28 +16,28 @@ Cloudflare Logpush supports pushing logs directly to Microsoft Azure via the Clo
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **Microsoft Azure**.
+4. In **Select a destination**, choose **Microsoft Azure**.
 
-6. Enter or select the following destination details:
+5. Enter or select the following destination details:
    - **SAS URL** - a pre-signed URL that grants access to Azure Storage resources. Refer to [Azure storage documentation](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer?tabs=macos#shared-access-signature-sas-url) for more information on generating a SAS URL using Azure Storage Explorer.
    - **Path** - bucket location within the storage container
    - **Organize logs into daily subfolders** (recommended)
 
 When you are done entering the destination details, select **Continue**.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ## Create and get access to a Blob Storage container
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/datadog.mdx

@@ -16,9 +16,9 @@ Cloudflare Logpush supports pushing logs directly to Datadog via the Cloudflare
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **Datadog**.
+4. In **Select a destination**, choose **Datadog**.
 
-6. Enter or select the following destination information:
+5. Enter or select the following destination information:
    - **Datadog URL Endpoint**, which can be either one below. You can find the difference at [Datadog API reference](https://docs.datadoghq.com/api/latest/logs/).
 
 <Tabs> <TabItem label="v1">
@@ -37,19 +37,19 @@ Cloudflare Logpush supports pushing logs directly to Datadog via the Cloudflare
 
 When you are done entering the destination details, select **Continue**.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ## Manage via API
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/google-cloud-storage.mdx

@@ -16,31 +16,31 @@ Cloudflare Logpush supports pushing logs directly to Google Cloud Storage (GCS)
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **Google Cloud Storage**.
+4. In **Select a destination**, choose **Google Cloud Storage**.
 
-6. Enter or select the following destination details:
+5. Enter or select the following destination details:
    - **Bucket** - GCS bucket name
    - **Path** - bucket location within the storage container
    - **Organize logs into daily subfolders** (recommended)
    - For **Grant Cloudflare access to upload files to your bucket**, make sure your bucket has added Cloudflare’s IAM as a user with a [Storage Object Admin role](https://cloud.google.com/storage/docs/access-control/iam-roles).
 
 When you are done entering the destination details, select **Continue**.
 
-7. To prove ownership, Cloudflare will send a file to your designated destination. To find the token, select the **Open** button in the **Overview** tab of the ownership challenge file, then paste it into the Cloudflare dashboard to verify your access to the bucket. Enter the **Ownership Token** and select **Continue**.
+6. To prove ownership, Cloudflare will send a file to your designated destination. To find the token, select the **Open** button in the **Overview** tab of the ownership challenge file, then paste it into the Cloudflare dashboard to verify your access to the bucket. Enter the **Ownership Token** and select **Continue**.
 
-8. Select the dataset to push to the storage service.
+7. Select the dataset to push to the storage service.
 
-9. In the next step, you need to configure your logpush job:
+8. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-10. In **Advanced Options**, you can:
+9. In **Advanced Options**, you can:
     - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
     - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
     - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-11. Select **Submit** once you are done configuring your logpush job.
+10. Select **Submit** once you are done configuring your logpush job.
 
 ## Create and get access to a GCS bucket
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/http.mdx

@@ -19,23 +19,23 @@ Cloudflare expects that the endpoint is available over HTTPS, using a trusted ce
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **HTTP destination**.
+4. In **Select a destination**, choose **HTTP destination**.
 
-6. Enter the **HTTP endpoint** where you want to send the logs to, and select **Continue**. - You can use `"header_*"` URL parameters to set request headers, for example, to pass an authentication token to your HTTP endpoint.
+5. Enter the **HTTP endpoint** where you want to send the logs to, and select **Continue**. - You can use `"header_*"` URL parameters to set request headers, for example, to pass an authentication token to your HTTP endpoint.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ## Manage via API
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/ibm-cloud-logs.mdx

@@ -16,28 +16,28 @@ Cloudflare Logpush supports pushing logs directly to IBM Cloud Logs via dashboar
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **IBM Cloud Logs**.
+4. In **Select a destination**, choose **IBM Cloud Logs**.
 
-6. Enter the following destination information:
+5. Enter the following destination information:
 
 - **HTTP Source Address** - For example, `ibmcl://<INSTANCE_ID>.ingress.<REGION>.logs.cloud.ibm.com/logs/v1/singles`.
 - **IBM API Key** - For more information refer to the [IBM Cloud Logs documentation](https://cloud.ibm.com/docs/cloud-logs).
 
 When you are done entering the destination details, select **Continue**.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ## Manage via API
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/new-relic.mdx

@@ -16,9 +16,9 @@ Cloudflare Logpush supports pushing logs directly to New Relic via the Cloudflar
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **New Relic**.
+4. In **Select a destination**, choose **New Relic**.
 
-6. Enter the **New Relic Logs Endpoint**:
+5. Enter the **New Relic Logs Endpoint**:
 
 <Tabs> <TabItem label="US">
 
@@ -34,19 +34,19 @@ Use the region that matches the one that has been set on your New Relic account.
 
 When you are done entering the destination details, select **Continue**.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ## Manage via API
 

src/content/docs/logs/logpush/logpush-job/enable-destinations/r2.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 40
 ---
 
-import { Render, APIRequest } from "~/components";
+import { Render, APIRequest, DashButton } from "~/components";
 
 Cloudflare Logpush supports pushing logs directly to R2. You can do so via the automatic setup (Cloudflare creates an R2 bucket for you), or you can create your own R2 bucket with the custom setup. The automatic setup is ideal for quickly setting up a bucket or for testing purposes. Instead, use the custom setup if you need full control over the configuration.
 
@@ -15,19 +15,13 @@ For more information about R2, refer to the [Cloudflare R2](/r2/) documentation.
 
 If you want to use the automatic setup for your logpush job:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
-
-2. Select the Enterprise account or domain (also known as zone) you want to use with Logpush. Depending on your choice, you have access to [account-scoped datasets](/logs/logpush/logpush-job/datasets/account/) and [zone-scoped datasets](/logs/logpush/logpush-job/datasets/zone/), respectively.
-
-3. Go to **Analytics & Logs** > **Logpush**.
-
-4. Select **Create a Logpush job**.
+<Render file="enable-logpush-job" product="logs" />
 
-5. Select **R2 Object Storage - automatic** as destination.
+4. Select **R2 Object Storage - automatic** as destination.
 
-6. Next, select the dataset and the storage region you want to use.
+5. Next, select the dataset and the storage region you want to use.
 
-7. To finalize, select **Create Logpush job**.
+6. To finalize, select **Create Logpush job**.
 
 Your setup should now be complete. If you require full control over the configuration, consider using the custom setup instead.
 
@@ -55,29 +49,29 @@ Before getting started:
 
 <Render file="enable-logpush-job" product="logs" />
 
-5. In **Select a destination**, choose **R2 Object Storage**.
+4. In **Select a destination**, choose **R2 Object Storage**.
 
-6. Enter or select the following destination details:
+5. Enter or select the following destination details:
    - **Bucket** - R2 bucket name
    - **Path** - bucket location, for example, `cloudflare-logs/http_requests/example.com`
    - **Organize logs into daily subfolders** (recommended)
    - Under **Authentication** add your **R2 Access Key ID** and **R2 Secret Access Key**. Refer to [Manage R2 API tokens](https://dash.cloudflare.com/b54f07a6c269ecca2fa60f1ae4920c99/r2/api-tokens) for more information.
 
 When you are done entering the destination details, select **Continue**.
 
-7. Select the dataset to push to the storage service.
+6. Select the dataset to push to the storage service.
 
-8. In the next step, you need to configure your logpush job:
+7. In the next step, you need to configure your logpush job:
    - Enter the **Job name**.
    - Under **If logs match**, you can select the events to include and/or remove from your logs. Refer to [Filters](/logs/logpush/logpush-job/filters/) for more information. Not all datasets have this option available.
    - In **Send the following fields**, you can choose to either push all logs to your storage destination or selectively choose which logs you want to push.
 
-9. In **Advanced Options**, you can:
+8. In **Advanced Options**, you can:
    - Choose the format of timestamp fields in your logs (`RFC3339`(default),`Unix`, or `UnixNano`).
    - Select a [sampling rate](/logs/logpush/logpush-job/api-configuration/#sampling-rate) for your logs or push a randomly-sampled percentage of logs.
    - Enable redaction for `CVE-2021-44228`. This option will replace every occurrence of `${` with `x{`.
 
-10. Select **Submit** once you are done configuring your logpush job.
+9. Select **Submit** once you are done configuring your logpush job.
 
 ### Manage via API
 
@@ -132,9 +126,11 @@ Once your logs are stored in R2, you can download them using various methods:
 
 ### Dashboard
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
+1. In the Cloudflare dashboard, go to the **R2** page.
+ 
+   <DashButton url="/?to=/:account/r2/overview" />
 
-2. Navigate to R2 and select your bucket.
+2. Select your bucket.
 
 3. From your bucket's page, locate the desired log file.