[Logs] Moves output options

public/__redirects

@@ -979,6 +979,7 @@
 /logs/get-started/alerts-and-analytics/ /logs/logpush/alerts-and-analytics/ 301
 /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
 
 # magic-firewall
 /magic-firewall/reference/examples/ /magic-firewall/how-to/add-rules/ 301

src/content/docs/bots/additional-configurations/detection-ids.mdx

@@ -53,7 +53,7 @@ You can create or edit existing Logpush jobs to include the new Bot Detection ID
 
 ### Via the API
 
-[Update your logpush job](/logs/reference/log-output-options/) by adding `BotDetectionIDs` to the  `output_options:`  parameters.
+[Update your logpush job](/logs/logpush/logpush-job/log-output-options/) by adding `BotDetectionIDs` to the  `output_options:`  parameters.
 
 ## Create or edit an expression
 

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

@@ -206,7 +206,7 @@ The kind parameter cannot be used to update existing Logpush jobs. You can only
 
 ## Options
 
-Logpull\_options has been replaced with Custom Log Formatting output\_options. Please refer to the [Log Output Options](/logs/reference/log-output-options/) documentation for instructions on configuring these options and updating your existing jobs to use these options.
+Logpull\_options has been replaced with Custom Log Formatting output\_options. Please refer to the [Log Output Options](/logs/logpush/logpush-job/log-output-options/) documentation for instructions on configuring these options and updating your existing jobs to use these options.
 
 If you are still using logpull\_options, here are the options that you can customize:
 

src/content/docs/logs/logpush/examples/example-logpush-curl.mdx

@@ -95,7 +95,7 @@ When using Sumo Logic, you may find it helpful to have [Live Tail](https://help.
 * **name** (optional) - We suggest using your domain name as the job name; the name cannot be changed after the job is created.
 * **destination\_conf** - Refer to [Destination](/logs/get-started/api-configuration/#destination) for details.
 * **dataset** - The category of logs you want to receive. Refer to [Log fields](/logs/reference/log-fields/) for the full list of supported datasets; this parameter cannot be changed after the job is created.
-* **output\_options** (optional) - Refer to [Log Output Options](/logs/reference/log-output-options/).
+* **output\_options** (optional) - Refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/).
   * Typically includes the desired fields and timestamp format.
   * Set the timestamp format to `RFC 3339` (`&timestamps=rfc3339`) for:
     * Google BigQuery usage.

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

@@ -96,7 +96,7 @@ To create a job, make a `POST` request to the Logpush jobs endpoint with the fol
 ```
 
 * **dataset** - The category of logs you want to receive. Refer to [Log fields](/logs/reference/log-fields/) for the full list of supported datasets.
-* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/reference/log-output-options/).
+* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/).
 
 Example request using cURL:
 

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

@@ -48,7 +48,7 @@ The supported parameters are as follows:
 * Fields that are unchanged from other sources:
   * **dataset** (required): For example, `http_requests`.
   * **name** (optional): We suggest using your domain name as the job name.
-  * **output\_options** (optional): Refer to [Log Output Options](/logs/reference/log-output-options/) to configure fields, sample rate, and timestamp format.
+  * **output\_options** (optional): Refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/) to configure fields, sample rate, and timestamp format.
 * Unique fields:
   * **destination\_conf**: Where to send the logs. This consists of an endpoint URL and HTTP headers used.
     * Any `"header_*"` URL parameters will be used to set request headers.

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

@@ -59,7 +59,7 @@ To create a job, make a `POST` request to the Logpush jobs endpoint with the fol
 
 * **name** (optional) - Use your domain name as the job name.
 
-* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/reference/log-output-options/).
+* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/).
 
   :::note[Note]
 

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

@@ -92,7 +92,7 @@ To create a job, make a `POST` request to the Logpush jobs endpoint with the fol
 :::
 
 * **dataset** - The category of logs you want to receive. Refer to [Log fields](/logs/reference/log-fields/) for the full list of supported datasets.
-* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/reference/log-output-options/).
+* **output\_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/).
 
 Example request using cURL:
 

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

@@ -85,7 +85,7 @@ Cloudflare highly recommends setting this value to <code class="InlineCode">fals
 
 - **dataset** - The category of logs you want to receive. Refer to [Log fields](/logs/reference/log-fields/) for the full list of supported datasets.
 
-- **output_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/reference/log-output-options/). For timestamp, Cloudflare recommends using `timestamps=rfc3339`.
+- **output_options** (optional) - To configure fields, sample rate, and timestamp format, refer to [Log Output Options](/logs/logpush/logpush-job/log-output-options/). For timestamp, Cloudflare recommends using `timestamps=rfc3339`.
 
 Example request using cURL:
 

src/content/docs/logs/reference/log-output-options.mdx → src/content/docs/logs/logpush/logpush-job/log-output-options.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: concept
 title: Log Output Options
 sidebar:
-  order: 39
+  order: 6
 
 ---
 

src/content/docs/logs/reference/log-fields/account/device_posture_results.md

@@ -109,7 +109,7 @@ The UUID of the device registration associated with this posture result.
 
 Type: `int or string`
 
-The date and time the corresponding device posture upload was performed (for example, '2021-07-27T00:01:07Z'). To specify the timestamp format, refer to [Output types](/logs/reference/log-output-options/#output-types).
+The date and time the corresponding device posture upload was performed (for example, '2021-07-27T00:01:07Z'). To specify the timestamp format, refer to [Output types](/logs/logpush/logpush-job/log-output-options/#output-types).
 
 ## UserUID
 

src/content/docs/logs/reference/log-fields/account/email_security_alerts.md

@@ -157,7 +157,7 @@ Threat categories attributed by Email Security processing (for example, 'Credent
 
 Type: `int or string`
 
-Start time of message processing (for example, '2024-08-28T15:32:35Z'). To specify the timestamp format, refer to [Output types](/logs/reference/log-output-options/#output-types).
+Start time of message processing (for example, '2024-08-28T15:32:35Z'). To specify the timestamp format, refer to [Output types](/logs/logpush/logpush-job/log-output-options/#output-types).
 
 ## To