From 2e9c8707893b38c7c1c42d5d85897312f4fde6e9 Mon Sep 17 00:00:00 2001
From: Sohei Gallagher <sohei@cloudflare.com>
Date: Thu, 20 Feb 2025 16:52:44 -0800
Subject: [PATCH] [Logs] Update Log fields

This updates Log fields.

They are synced from internal `entities` repo's fields templates.
---
 .../log-fields/zone/http_requests.md          |  8 ++-
 .../reference/log-fields/zone/zaraz_events.md | 52 +++++++++++++++++++
 2 files changed, 59 insertions(+), 1 deletion(-)
 create mode 100644 src/content/docs/logs/reference/log-fields/zone/zaraz_events.md

diff --git a/src/content/docs/logs/reference/log-fields/zone/http_requests.md b/src/content/docs/logs/reference/log-fields/zone/http_requests.md
index a9a51890886955e..f7b624e7a2dc4c1 100644
--- a/src/content/docs/logs/reference/log-fields/zone/http_requests.md
+++ b/src/content/docs/logs/reference/log-fields/zone/http_requests.md
@@ -481,7 +481,7 @@ Action of the security rule that triggered a terminating action, if any.
 
 Type: `array[string]`
 
-Array of actions the Cloudflare security products performed on this request. The individual security products associated with this action can be found in SecuritySources and their respective rule Ids can be found in SecurityRuleIDs. The length of the array is the same as SecurityRuleIDs and SecuritySources. <br />Possible actions are <em>unknown</em> \| <em>allow</em> \| <em>block</em> \| <em>challenge</em> \| <em>jschallenge</em> \| <em>log</em> \| <em>connectionClose</em> \| <em>challengeSolved</em> \| <em>challengeBypassed</em> \| <em>jschallengeSolved</em> \| <em>jschallengeBypassed</em> \| <em>bypass</em> \| <em>managedChallenge</em> \| <em>managedChallengeNonInteractiveSolved</em> \| <em>managedChallengeInteractiveSolved</em> \| <em>managedChallengeBypassed</em> \| <em>rewrite</em> \| <em>forceConnectionClose</em> \| <em>skip</em>.
+Array of actions the Cloudflare security products performed on this request. The individual security products associated with this action can be found in SecuritySources and their respective rule IDs can be found in SecurityRuleIDs. The length of the array is the same as SecurityRuleIDs and SecuritySources. <br />Possible actions are <em>unknown</em> \| <em>allow</em> \| <em>block</em> \| <em>challenge</em> \| <em>jschallenge</em> \| <em>log</em> \| <em>connectionClose</em> \| <em>challengeSolved</em> \| <em>challengeBypassed</em> \| <em>jschallengeSolved</em> \| <em>jschallengeBypassed</em> \| <em>bypass</em> \| <em>managedChallenge</em> \| <em>managedChallengeNonInteractiveSolved</em> \| <em>managedChallengeInteractiveSolved</em> \| <em>managedChallengeBypassed</em> \| <em>rewrite</em> \| <em>forceConnectionClose</em> \| <em>skip</em>.
 
 ## SecurityRuleDescription
 
@@ -561,6 +561,12 @@ Type: `int`
 
 Amount of time in microseconds spent executing a worker, if any.
 
+## WorkerScriptName
+
+Type: `string`
+
+The worker script name that made the request.
+
 ## WorkerStatus
 
 Type: `string`
diff --git a/src/content/docs/logs/reference/log-fields/zone/zaraz_events.md b/src/content/docs/logs/reference/log-fields/zone/zaraz_events.md
new file mode 100644
index 000000000000000..c1f33e1edb675e0
--- /dev/null
+++ b/src/content/docs/logs/reference/log-fields/zone/zaraz_events.md
@@ -0,0 +1,52 @@
+---
+# Code generator. DO NOT EDIT.
+
+title: Zaraz Events
+pcx_content_type: configuration
+sidebar:
+  order: 21
+---
+
+The descriptions below detail the fields available for `zaraz_events`.
+
+## Body
+
+Type: `object`
+
+Zaraz incoming request body.
+
+## EventDetails
+
+Type: `object`
+
+Zaraz log event details.
+
+## EventType
+
+Type: `string`
+
+Zaraz log event name.
+
+## IP
+
+Type: `string`
+
+Zaraz incoming request client IP address.
+
+## RequestHeaders
+
+Type: `object`
+
+Zaraz incoming request headers.
+
+## TimestampStart
+
+Type: `int or string`
+
+Zaraz log event timestamp.
+
+## URL
+
+Type: `string`
+
+Zaraz incoming request URL.