Moves Log Fields (#23950)

Author: angelampcosta

public/__redirects

@@ -956,7 +956,7 @@
 /load-balancing/local-traffic-management/ltm-magic-wan/ /load-balancing/private-network/magic-wan/ 301
 
 # logs
-/logs/log-fields/ /logs/reference/log-fields/ 301
+/logs/log-fields/ /logs/logpush/logpush-job/datasets/ 301
 /logs/logpull-api/ /logs/logpull/ 301
 /logs/logpull-api/requesting-logs/ /logs/logpull/requesting-logs/ 301
 /logs/logpush/aws-s3/ /logs/logpush/logpush-job/enable-destinations/aws-s3/ 301
@@ -2215,6 +2215,7 @@
 /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
+/logs/reference/log-fields/* /logs/logpush/logpush-job/datasets/: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/access/2025-01-15-ssh-logs-and-logpush.mdx

@@ -8,6 +8,6 @@ date: 2025-01-15
 Only available on Enterprise plans.
 :::
 
-Cloudflare now allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. Once exported, analyze and audit the data as best fits your organization! For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
+Cloudflare now allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. Once exported, analyze and audit the data as best fits your organization! For a list of available data fields, refer to the [SSH logs dataset](/logs/logpush/logpush-job/datasets/account/ssh_logs/).
 
 To set up a Logpush job, refer to [Logpush integration](/cloudflare-one/insights/logs/logpush/).

src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx

@@ -4,7 +4,7 @@ description: User action logs for Remote Browser Isolation
 date: 2025-03-04
 ---
 
-We're excited to announce that new logging capabilities for [Remote Browser Isolation (RBI)](/cloudflare-one/policies/browser-isolation/) through [Logpush](/logs/reference/log-fields/account/) are available in Beta starting today!
+We're excited to announce that new logging capabilities for [Remote Browser Isolation (RBI)](/cloudflare-one/policies/browser-isolation/) through [Logpush](/logs/logpush/logpush-job/datasets/account/) are available in Beta starting today!
 
 With these enhanced logs, administrators can gain visibility into end user behavior in the remote browser and track blocked data extraction attempts, along with the websites that triggered them, in an isolated session.
 

src/content/changelog/workers/2025-04-07-increase-trace-events-limit.mdx

@@ -9,7 +9,7 @@ date: 2025-04-07
 You can now capture a maximum of 256 KB of log events per Workers invocation, helping you gain better visibility into application behavior.
 
 All console.log() statements, exceptions, request metadata, and headers are automatically captured during the Worker invocation and emitted
-as [JSON object](/logs/reference/log-fields/account/workers_trace_events). [Workers Logs](/workers/observability/logs/workers-logs) deserializes
+as [JSON object](/logs/logpush/logpush-job/datasets/account/workers_trace_events). [Workers Logs](/workers/observability/logs/workers-logs) deserializes
 this object before indexing the fields and storing them. You can also capture, transform, and export the JSON object in a
 [Tail Worker](/workers/observability/logs/tail-workers).
 

src/content/changelog/workers/2025-04-09-workers-timing.mdx

@@ -9,8 +9,8 @@ date: 2025-04-09
 You can now observe and investigate the CPU time and Wall time for every Workers Invocations.
 
 - For [Workers Logs](/workers/observability/logs/workers-logs), CPU time and Wall time are surfaced in the [Invocation Log](/workers/observability/logs/workers-logs/#invocation-logs)..
-- For [Tail Workers](/workers/observability/logs/tail-workers), CPU time and Wall time are surfaced at the top level of the [Workers Trace Events object](/logs/reference/log-fields/account/workers_trace_events).
-- For [Workers Logpush](/workers/observability/logs/logpush), CPU and Wall time are surfaced at the top level of the [Workers Trace Events object](/logs/reference/log-fields/account/workers_trace_events). All new jobs will have these new fields included by default. Existing jobs need to be updated to include CPU time and Wall time.
+- For [Tail Workers](/workers/observability/logs/tail-workers), CPU time and Wall time are surfaced at the top level of the [Workers Trace Events object](/logs/logpush/logpush-job/datasets/account/workers_trace_events).
+- For [Workers Logpush](/workers/observability/logs/logpush), CPU and Wall time are surfaced at the top level of the [Workers Trace Events object](/logs/logpush/logpush-job/datasets/account/workers_trace_events). All new jobs will have these new fields included by default. Existing jobs need to be updated to include CPU time and Wall time.
 
 You can use a Workers Logs filter to search for logs where Wall time exceeds 100ms.
 

src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx

@@ -83,7 +83,7 @@ To get more information about potential bot requests, use these JA3 and JA4 fing
 - [Bot Analytics](/bots/bot-analytics/#enterprise-bot-management)
 - [Security Events](/waf/analytics/security-events/) and [Security Analytics](/waf/analytics/security-analytics/)
 - [Analytics GraphQL API](/analytics/graphql-api/), specifically the **HTTP Requests** dataset
-- [Logs](/logs/reference/log-fields/zone/http_requests/)
+- [Logs](/logs/logpush/logpush-job/datasets/zone/http_requests/)
 
 ## Actions
 

src/content/docs/bots/reference/bot-management-variables.mdx

@@ -47,7 +47,7 @@ and cf.bot_management.score lt 30
 
 ## Log fields
 
-Once you enable Bot Management, Cloudflare also surfaces bot information in its [HTTP requests log fields](/logs/reference/log-fields/zone/http_requests/):
+Once you enable Bot Management, Cloudflare also surfaces bot information in its [HTTP requests log fields](/logs/logpush/logpush-job/datasets/zone/http_requests/):
 
 - BotDetectionIDs
 - BotScore

src/content/docs/cache/advanced-configuration/cache-reserve.mdx

@@ -61,7 +61,7 @@ Not all assets are eligible for Cache Reserve. To be admitted into Cache Reserve
 
 Like the standard CDN, Cache Reserve also uses the `cf-cache-status` header to indicate cache statuses like `MISS`, `HIT`, and `REVALIDATED`. Cache Reserve cache misses and hits are factored into the dashboard's cache hit ratio.
 
-Individual sampled requests that filled or were served by Cache Reserve are viewable via the [CacheReserveUsed](/logs/reference/log-fields/zone/http_requests/) Logpush field.
+Individual sampled requests that filled or were served by Cache Reserve are viewable via the [CacheReserveUsed](/logs/logpush/logpush-job/datasets/zone/http_requests/) Logpush field.
 
 Cache Reserve monthly operations and storage usage are viewable in the dashboard.
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/hostname-analytics.mdx

@@ -48,6 +48,6 @@ Build custom dashboards to share this information by specifying an individual cu
 
 Using [filters](/logs/logpush/logpush-job/filters/), you can send set sample rates (or not include logs altogether) based on filter criteria. This flexibility allows you to maintain selective logs for custom hostnames without massively increasing your log volume.
 
-Filtering is available for [all Cloudflare datasets](/logs/reference/log-fields/zone/).
+Filtering is available for [all Cloudflare datasets](/logs/logpush/logpush-job/datasets/zone/).
 
 <Render file="filtering-limitations" product="logs" />

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx

@@ -149,7 +149,7 @@ To manually retrieve logs:
 Only available on Enterprise plans.
 :::
 
-Cloudflare allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. For a list of available data fields, refer to the [SSH logs dataset](/logs/reference/log-fields/account/ssh_logs/).
+Cloudflare allows you to send SSH command logs to storage destinations configured in [Logpush](/logs/logpush/), including third-party destinations. For a list of available data fields, refer to the [SSH logs dataset](/logs/logpush/logpush-job/datasets/account/ssh_logs/).
 
 To set up the Logpush job, refer to [Logpush integration](/cloudflare-one/insights/logs/logpush/).