Skip to content

[Logs] Update Logpush dataset field definitions (2026-08-07) - #32603

Open
soheiokamoto wants to merge 1 commit into
productionfrom
sync/log-fields-2026-08-07
Open

[Logs] Update Logpush dataset field definitions (2026-08-07)#32603
soheiokamoto wants to merge 1 commit into
productionfrom
sync/log-fields-2026-08-07

Conversation

@soheiokamoto

Copy link
Copy Markdown
Contributor

Summary

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

Updated fields in existing datasets

  • Firewall events (added): AISecurityCustomTopicCategories.
  • Gateway HTTP (added): ExperimentalFeatures and PackageInfo.
  • Firewall events (added): AISecurityCustomTopicCategories.
  • HTTP requests (added): AISecurityCustomTopicCategories and ClientTLSKeyExchangeGroup.

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-08-07-log-fields-updated.mdx — changelog

Documentation checklist

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

@soheiokamoto
soheiokamoto requested review from a team, hoan-pom and rianvdm as code owners August 7, 2026 14:23
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 1 warning, 💡 1 suggestion found in commit 13e1ba6.

👉 Fix in your agent 👈
Fix the following review findings in PR #32603 (https://github.com/cloudflare/cloudflare-docs/pull/32603).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-976b94949e96 · Duplicate changelog entry
- **File:** `src/content/changelog/logs/2026-08-07-log-fields-updated.mdx` line 13
- **Issue:** The exact same bullet point `**Firewall events** (added): \`AISecurityCustomTopicCategories\`.` already appears on line 11 and is repeated on line 13.
- **Fix:** Remove the duplicate line 13 so the Firewall events update is listed only once.

---

## Style Guide Review

### Suggestions (1)

#### SG-2bd4a5fa2820 · Passive voice
- **File:** `src/content/changelog/logs/2026-08-07-log-fields-updated.mdx` line 3
- **Issue:** Frontmatter description: "Fields have been updated across multiple Logpush datasets in Cloudflare Logs."
- **Fix:** Rewrite in active voice, e.g. "Updates fields across multiple Logpush datasets in Cloudflare Logs."

Code Review

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

Warnings (1)
File Issue
changelog/logs/2026-08-07-log-fields-updated.mdx line 13 Duplicate changelog entry — The exact same bullet point \*\*Firewall events\*\* (added): \AISecurityCustomTopicCategories`.` already appears on line 11 and is repeated on line 13. Fix: Remove the duplicate line 13 so the Firewall events update is listed only once.

Conventions

No convention issues found.

Style Guide Review

Suggestions (1)
File Issue
changelog/logs/2026-08-07-log-fields-updated.mdx line 3 Passive voice — Frontmatter description: "Fields have been updated across multiple Logpush datasets in Cloudflare Logs." Fix: Rewrite in active voice, e.g. "Updates fields across multiple Logpush datasets in Cloudflare Logs."
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.
/rebase Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants