[Logs] Moves Custom fields

public/__redirects

@@ -980,6 +980,7 @@
 /logs/edge-log-delivery/ /logs/logpush/logpush-job/edge-log-delivery/ 301
 /logs/reference/filters/ /logs/logpush/logpush-job/filters/ 301
 /logs/reference/log-output-options/ /logs/logpush/logpush-job/log-output-options/ 301
+/logs/reference/custom-fields/ /logs/logpush/logpush-job/custom-fields/ 301
 
 # magic-firewall
 /magic-firewall/reference/examples/ /magic-firewall/how-to/add-rules/ 301

src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx

@@ -20,4 +20,4 @@ These defaults can be overidden to suit your logging needs.
 Transformed and raw values for request and response headers are available **only via the API** and cannot be set through the UI.
 :::
 
-For more information refer to [Custom fields](/logs/reference/custom-fields/) documentation
+For more information refer to [Custom fields](/logs/logpush/logpush-job/custom-fields/) documentation

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

@@ -157,6 +157,6 @@ When a user requests a given URL, Access appends the user identity from that tok
 
 ### Using the `cf-access-user` field
 
-In addition to the HTTP request fields available in Cloudflare Enterprise logging, requests made to applications behind Access include the `cf-access-user` field, which contains the user identity string. This offers another tool for auditing user behavior. To add the `cf-access-user` field to your HTTP request logs, you must add it as a custom field. Refer to [Custom fields](/logs/reference/custom-fields/) for instructions.
+In addition to the HTTP request fields available in Cloudflare Enterprise logging, requests made to applications behind Access include the `cf-access-user` field, which contains the user identity string. This offers another tool for auditing user behavior. To add the `cf-access-user` field to your HTTP request logs, you must add it as a custom field. Refer to [Custom fields](/logs/logpush/logpush-job/custom-fields/) for instructions.
 
 Keep in mind that Access does not log all interactions. For example, per-request audit logs can indicate that a specific user visited `domain.com/admin` and then `domain.com/admin/panel`, but the logs can only identify user interactions that result in a new HTTP request.

src/content/docs/logs/get-started/api-configuration.mdx

@@ -262,7 +262,7 @@ These parameters can be used to gain control of batch size in the case that a de
 
 ## Custom fields
 
-You can add custom fields to your HTTP request log entries in the form of HTTP request headers, HTTP response headers, and cookies. Custom fields configuration applies to all the Logpush jobs in a zone that use the HTTP requests dataset. To learn more, refer to [Custom fields](/logs/reference/custom-fields/).
+You can add custom fields to your HTTP request log entries in the form of HTTP request headers, HTTP response headers, and cookies. Custom fields configuration applies to all the Logpush jobs in a zone that use the HTTP requests dataset. To learn more, refer to [Custom fields](/logs/logpush/logpush-job/custom-fields/).
 
 ## Audit
 

src/content/docs/logs/reference/custom-fields.mdx → src/content/docs/logs/logpush/logpush-job/custom-fields.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: how-to
 title: Custom fields
 sidebar:
-  order: 43
+  order: 8
 ---
 
 import { APIRequest } from "~/components";

src/content/docs/logs/reference/log-fields/index.mdx

@@ -27,7 +27,7 @@ The `<DATASET>` argument indicates the log category. For example, `http_requests
 
 * The availability of Logpush dataset fields depends on your subscription plan.
 * Zone-scoped HTTP requests are available in both Logpush and Logpull.
-* [Custom fields](/logs/reference/custom-fields/) for HTTP requests are only available in Logpush.
+* [Custom fields](/logs/logpush/logpush-job/custom-fields/) for HTTP requests are only available in Logpush.
 * All other datasets are only available through Logpush.
 
 ## Deprecation

src/content/docs/logs/reference/log-fields/zone/http_requests.md

@@ -247,7 +247,7 @@ List of content types.
 
 Type: `object`
 
-String key-value pairs for Cookies. This field is populated based on [Logpush Custom fields](/logs/reference/custom-fields/), which need to be configured.
+String key-value pairs for Cookies. This field is populated based on [Logpush Custom fields](/logs/logpush/logpush-job/custom-fields/), which need to be configured.
 
 ## EdgeCFConnectingO2O
 
@@ -463,13 +463,13 @@ ID of the request.
 
 Type: `object`
 
-String key-value pairs for RequestHeaders. This field is populated based on [Logpush Custom fields](/logs/reference/custom-fields/), which need to be configured.
+String key-value pairs for RequestHeaders. This field is populated based on [Logpush Custom fields](/logs/logpush/logpush-job/custom-fields/), which need to be configured.
 
 ## ResponseHeaders
 
 Type: `object`
 
-String key-value pairs for ResponseHeaders. This field is populated based on [Logpush Custom fields](/logs/reference/custom-fields/), which need to be configured.
+String key-value pairs for ResponseHeaders. This field is populated based on [Logpush Custom fields](/logs/logpush/logpush-job/custom-fields/), which need to be configured.
 
 ## SecurityAction
 

src/content/docs/ruleset-engine/reference/phases-list.mdx

@@ -67,4 +67,4 @@ The phases execute in the order they appear in the table.
 | `http_ratelimit`                  | [Rate limiting rules](/waf/rate-limiting-rules/) (when they use response information) |
 | `http_response_compression`       | [Compression Rules](/rules/compression-rules/)                                        |
 | `http_response_firewall_managed`  | [Cloudflare Sensitive Data Detection](/waf/managed-rules/) (Data Loss Prevention)     |
-| `http_log_custom_fields`          | [Logpush custom fields](/logs/reference/custom-fields/)                               |
+| `http_log_custom_fields`          | [Logpush custom fields](/logs/logpush/logpush-job/custom-fields/)                               |