[Logs] Moves enable destinations (#23830)

* Moves enable destinations

* Apply suggestions from code review

Author: angelampcosta

public/__redirects

@@ -569,7 +569,7 @@
 /fundamentals/speed/aim/ /speed/aim/ 301
 /fundamentals/speed/optimization/ /speed/optimization/ 301
 /fundamentals/speed/prefetch-urls/ /speed/optimization/content/prefetch-urls/ 301
-/fundamentals/data-products/analytics-integrations/sumo-logic/ /logs/get-started/enable-destinations/sumo-logic/ 301
+/fundamentals/data-products/analytics-integrations/sumo-logic/ /logs/logpush/logpush-job/enable-destinations/sumo-logic/ 301
 /support/account-management-billing/account-management/adding-multiple-sites-to-cloudflare-via-automation/ /fundamentals/manage-domains/add-multiple-sites-automation/ 301
 /support/account-management-billing/account-privacy-and-security/securing-user-access-with-two-factor-authentication-2fa/ /fundamentals/user-profiles/2fa/ 301
 /support/account-management-billing/account-privacy-and-security/multi-factor-email-authentication/ /fundamentals/user-profiles/multi-factor-email-authentication/ 301
@@ -957,13 +957,13 @@
 /logs/log-fields/ /logs/reference/log-fields/ 301
 /logs/logpull-api/ /logs/logpull/ 301
 /logs/logpull-api/requesting-logs/ /logs/logpull/requesting-logs/ 301
-/logs/logpush/aws-s3/ /logs/get-started/enable-destinations/aws-s3/ 301
-/logs/logpush/azure/ /logs/get-started/enable-destinations/azure/ 301
-/logs/logpush/google-cloud-storage/ /logs/get-started/enable-destinations/google-cloud-storage/ 301
-/logs/logpush/logpush-configuration-api/ /logs/get-started/enable-destinations/ 301
+/logs/logpush/aws-s3/ /logs/logpush/logpush-job/enable-destinations/aws-s3/ 301
+/logs/logpush/azure/ /logs/logpush/logpush-job/enable-destinations/azure/ 301
+/logs/logpush/google-cloud-storage/ /logs/logpush/logpush-job/enable-destinations/google-cloud-storage/ 301
+/logs/logpush/logpush-configuration-api/ /logs/logpush/logpush-job/enable-destinations/ 301
 /logs/logpush/logpush-configuration-api/understanding-logpush-api/ /logs/get-started/api-configuration/ 301
-/logs/logpush/logpush-dashboard/ /logs/get-started/enable-destinations/ 301
-/logs/logpush/s3-compatible-endpoints/ /logs/get-started/enable-destinations/s3-compatible-endpoints/ 301
+/logs/logpush/logpush-dashboard/ /logs/logpush/logpush-job/enable-destinations/ 301
+/logs/logpush/s3-compatible-endpoints/ /logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints/ 301
 /logs/reference/logpush-api-configuration/ /logs/get-started/api-configuration/ 301
 /logs/reference/logpush-api-configuration/filters/ /logs/reference/filters/ 301
 # Non-slashed version is being used in the Cloudflare dashboard
@@ -2177,6 +2177,7 @@
 /fundamentals/setup/account/* /fundamentals/account/:splat 301
 /fundamentals/setup/manage-domains/* /fundamentals/manage-domains/:splat 301
 /fundamentals/setup/manage-members/* /fundamentals/manage-members/:splat 301
+/logs/get-started/enable-destinations/* /logs/logpush/logpush-job/enable-destinations/:splat 301
 
 # Cloudflare One / Zero Trust
 /cloudflare-one/connections/connect-networks/install-and-setup/tunnel-guide/local/as-a-service/* /cloudflare-one/connections/connect-networks/configure-tunnels/local-management/as-a-service/:splat 301

src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx

@@ -10,6 +10,6 @@ Now, you no longer need to navigate multiple pages to manually create an R2 buck
 
 This enhancement makes it easier for customers to adopt Logpush and R2.
 
-For more details refer to our [Logs](/logs/get-started/enable-destinations/r2/) documentation.
+For more details refer to our [Logs](/logs/logpush/logpush-job/enable-destinations/r2/) documentation.
 
 ![One-click Logpush to R2](src/assets/images/changelog/logs/Oneclick.gif)

src/content/docs/analytics/analytics-integrations/new-relic.mdx

@@ -13,7 +13,7 @@ Before sending your Cloudflare log data to New Relic, make sure that you:
 
 - Have a Cloudflare Enterprise account with Cloudflare Logs enabled.
 - Have a New Relic account.
-- Configure [Logpush to New Relic](/logs/get-started/enable-destinations/new-relic/).
+- Configure [Logpush to New Relic](/logs/logpush/logpush-job/enable-destinations/new-relic/).
 
 ## Task 1 - Install the Cloudflare Network Logs quickstart
 

src/content/docs/analytics/analytics-integrations/sentinel.mdx

@@ -10,7 +10,7 @@ Microsoft has developed a Cloudflare connector that allows their customers to in
 
 ## How it works
 
-[Logpush](/logs/get-started/enable-destinations/azure/) sends logs from Cloudflare to Azure Blob Storage. From there, the Cloudflare connector, a Microsoft function, ingests these logs into Azure Log Analytics Workspace, making them available for monitoring and analysis in Microsoft Sentinel.
+[Logpush](/logs/logpush/logpush-job/enable-destinations/azure/) sends logs from Cloudflare to Azure Blob Storage. From there, the Cloudflare connector, a Microsoft function, ingests these logs into Azure Log Analytics Workspace, making them available for monitoring and analysis in Microsoft Sentinel.
 
 ![Sentinel integrations steps](~/assets/images/analytics/sentinel-diagram.png)
 

src/content/docs/analytics/analytics-integrations/splunk.mdx

@@ -86,9 +86,9 @@ You can also manually configure Data Models by going to **Settings** > **Data mo
 
 ## Task 2 - Make the API call to create the Logpush job
 
-Create the Logpush job by following the instructions on [Enable Logpush to Splunk](/logs/get-started/enable-destinations/splunk/). The API call creates a Logpush job but does not enable it.
+Create the Logpush job by following the instructions on [Enable Logpush to Splunk](/logs/logpush/logpush-job/enable-destinations/splunk/). The API call creates a Logpush job but does not enable it.
 
-Enable the Logpush job through the Cloudflare dashboard or through the API by following the instructions on [Enable Logpush to Splunk](/logs/get-started/enable-destinations/splunk/). To enable through the dashboard:
+Enable the Logpush job through the Cloudflare dashboard or through the API by following the instructions on [Enable Logpush to Splunk](/logs/logpush/logpush-job/enable-destinations/splunk/). To enable through the dashboard:
 
 1. Navigate to the Cloudflare dashboard and select **Analytics & Logs** > **Logs**.
 2. Select **Edit** and select the fields referenced in the Dashboard section below to fully populate all tables and graphs.

src/content/docs/analytics/network-analytics/get-started.mdx

@@ -28,7 +28,7 @@ Use the [GraphQL Analytics API](/analytics/graphql-api/) to query data using the
 
 ## Send Network Analytics logs to a third-party service
 
-[Create a Logpush job](/logs/get-started/enable-destinations/) that sends Network analytics logs to your storage service, <GlossaryTooltip term="SIEM">SIEM solution</GlossaryTooltip>, or log management provider.
+[Create a Logpush job](/logs/logpush/logpush-job/enable-destinations/) that sends Network analytics logs to your storage service, <GlossaryTooltip term="SIEM">SIEM solution</GlossaryTooltip>, or log management provider.
 
 ## Limitations
 

src/content/docs/cloudflare-one/insights/logs/enable-logs.mdx

@@ -11,15 +11,15 @@ Email Security allows you to configure Logpush to send detection data to an endp
 
 Detection logs generate logs made by Email Security and some of the metadata associated with the detection.
 
-To enable detection logs, refer to [Enable destinations](/logs/get-started/enable-destinations/).
+To enable detection logs, refer to [Enable destinations](/logs/logpush/logpush-job/enable-destinations/).
 
 If you enable detection logs using [R2](/r2/), choose **Email security alerts** when configuring the **Dataset**.
 
 ## Enable user action logs
 
 User action logs allow you to view logs regarding all actions taken via the [API](/api/resources/email_security/) or the dashboard.
 
-Before you can enable audit logs for Email Security, you will have to enable logpush jobs to your storage destination. Refer to [Enable destinations](/logs/get-started/enable-destinations/) to enable logs on destinations such as Cloudflare R2, HTTP, Amazon S3, and more.
+Before you can enable audit logs for Email Security, you will have to enable logpush jobs to your storage destination. Refer to [Enable destinations](/logs/logpush/logpush-job/enable-destinations/) to enable logs on destinations such as Cloudflare R2, HTTP, Amazon S3, and more.
 
 Once you have configured your destination, you can set up audit logs for user action:
 

src/content/docs/cloudflare-one/insights/logs/logpush.mdx

@@ -14,15 +14,15 @@ With Cloudflare's [Logpush](/logs/logpush/) service, you can configure the autom
 ## Export Zero Trust logs with Logpush
 
 :::caution[Dashboard limitation]
-Zero Trust does not support configuring [Cloudflare R2](/logs/get-started/enable-destinations/r2/) as a Logpush destination in the dashboard. To use R2 as a destination for Zero Trust logs, configure your Logpush jobs [with the API](/logs/get-started/enable-destinations/r2/#manage-via-api).
+Zero Trust does not support configuring [Cloudflare R2](/logs/logpush/logpush-job/enable-destinations/r2/) as a Logpush destination in the dashboard. To use R2 as a destination for Zero Trust logs, configure your Logpush jobs [with the API](/logs/logpush/logpush-job/enable-destinations/r2/#manage-via-api).
 :::
 
 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**.
-4. Choose a [Logpush destination](/logs/get-started/enable-destinations/).
+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.
 7. Enter a **Job name**, any [filters](/logs/reference/filters/) you would like to add, and the data fields you want to include in the logs.

src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx

@@ -82,7 +82,7 @@ To set up the DLP Forensic Copy Logpush job:
 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**.
-4. Choose a [Logpush destination](/logs/get-started/enable-destinations/).
+4. Choose a [Logpush destination](/logs/logpush/logpush-job/enable-destinations/).
 5. In **Configure logpush job**, choose the _DLP forensic copies_ dataset. Select **Create Logpush job**.
 6. Return to Zero Trust and go to **Gateway** > **Firewall policies** > **HTTP**.
 7. Edit an existing Allow or Block policy, or [create a new policy](/cloudflare-one/policies/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy). Your policy does not need to include a DLP profile.

src/content/docs/data-localization/how-to/r2.mdx

@@ -79,7 +79,7 @@ This command will output a hash similar to `dxxxx391b`.
 
 </Details>
 
-3. Set up a Logpush destination using [S3-compatible endpoint](/logs/get-started/enable-destinations/s3-compatible-endpoints/) and fill in the following fields:
+3. Set up a Logpush destination using [S3-compatible endpoint](/logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints/) and fill in the following fields:
 
 - **Bucket**: Enter the name of the R2 bucket you created with the jurisdiction you would like to use.
 - **Path** (optional): If you want, you can specify a folder path to organize your logs.