[Logs] Update Logpush dataset field definitions (2026-07-02)

[soheiokamoto]

Summary

Automated sync of Logpush dataset field definitions from data/entities.

Updated fields in existing datasets

• Gateway DNS (added): AppliedMaxTTL and UpstreamRecordTTLs.
• Gateway HTTP (added): Warnings.
• HTTP requests (added): CacheLockWaitedMs.

Files changed

• src/content/docs/logs/logpush/logpush-job/datasets/account/ — dataset pages
• src/content/docs/logs/logpush/logpush-job/datasets/zone/ — dataset pages
• src/content/changelog/logs/2026-07-02-log-fields-updated.mdx — changelog

Documentation checklist

• Changelog entry added
• Content generated by code generator (DO NOT EDIT manually)

[soheiokamoto]

/bonk please review this automated sync of Logpush dataset field definitions.

Focus on the following:

1. Changelog quality — is the entry clear, accurate, and useful to end users?

2. Field description quality — are the descriptions accurate, clear, and complete?

3. Manual edits at risk of being overwritten — are there any field descriptions that appear
   to have been manually edited directly in cloudflare-docs (e.g. contain context or guidance
   not present in the machine-generated description format)? If so, flag them so the author can
   preserve those edits in the internal source YAML.

[cloudflare-docs-bot]

Review

✅ No issues found in commit 843bd08.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

_{No code review issues found.}

Conventions

Checks PR title, description, and redirect checklist.

_{No convention issues found.}

Style Guide Review

_{No style-guide issues found.}

Redirects

_{No missing redirect entries found.}

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/changelog/	@cloudflare/pm-changelogs, @cloudflare/product-owners
/src/content/docs/logs/	@soheiokamoto, @angelampcosta, @rianvdm, @dcpena, @cloudflare/product-owners

[ask-bonk]

Here's my review of PR #31856.

---

1. Changelog quality

The changelog entry is clear, accurate, and follows the standard format. The description is concise and links to the relevant datasets page.

One omission: The PR also updates workers_trace_events.md (expanding EventType and Outcome enum values), but the changelog only lists Gateway DNS, Gateway HTTP, and HTTP requests. Consider adding Workers Trace Events to the changelog so users know that dataset was updated too.

2. Field description quality

The new field descriptions are accurate and well-formed:

• AppliedMaxTTL (Gateway DNS) — Clear definition, specifies units (seconds), and notes the zero-value case.
• UpstreamRecordTTLs (Gateway DNS) — Good detail, includes an example array and notes the one-to-one mapping with resource records.
• Warnings (Gateway HTTP) — Simple and accurate.
• CacheLockWaitedMs (HTTP requests) — Clear definition with units (milliseconds) and scope ("across all cache tiers").

The enum expansions in workers_trace_events.md (EventType and Outcome) are also correct and consistent with the existing formatting.

3. Manual edits at risk of being overwritten

While these files are marked as code-generated, src/content/docs/logs/logpush/logpush-job/datasets/zone/http_requests.md contains several field descriptions with documentation-specific cross-references and guidance that look like they may have been manually enriched in the past. If these were added directly in this repo rather than in the internal source YAML, future syncs may silently revert them.

Please verify that the following descriptions (or their equivalents) exist in the internal source YAML so they are preserved on the next generation:

• OriginResponseBytes — Contains detailed guidance ("Consider using CacheResponseBytes and filtering out OriginResponseStatus with values 0 and 304…") and a link to /logs/faq/common-calculations/#how-can-i-calculate-bytes-served-by-the-origin-from-cloudflare-logs.
• ClientRequestSource — Contains a cross-reference link to /logs/reference/clientrequestsource/.
• CacheCacheStatus — Contains a link to /cache/concepts/cache-responses/ and extra prose explaining the "dynamic" value.
• LeakedCredentialCheckResult — Contains a link to /waf/detections/leaked-credentials/.
• BotTags — Contains a link to /bots/concepts/bot-tags/.

The Bot Management fields also contain repeated boilerplate ("Available only for Bot Management customers. To enable this feature, contact your account team.") that should be preserved in the generator source if it isn't already.

Action requested: Confirm these enrichments are in the source YAML, or port them there before this is considered fully safe from future overwrites.

github run

[github-actions]

Preview URL: https://843bd081.preview.developers.cloudflare.com
Preview Branch URL: https://sync-log-fields-2026-07-02.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/changelog/post/2026-07-02-log-fields-updated/	https://sync-log-fields-2026-07-02.preview.developers.cloudflare.com/changelog/post/2026-07-02-log-fields-updated/