[Logs] Update Logpush dataset field definitions (2026-06-22)#31626
[Logs] Update Logpush dataset field definitions (2026-06-22)#31626soheiokamoto wants to merge 1 commit into
Conversation
|
/bonk please review this automated sync of Logpush dataset field definitions. Focus on the following:
|
Review
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. Warnings (1)
Style Guide ReviewWarnings (1)
Suggestions (1)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
There was a problem hiding this comment.
Automated sync of Logpush dataset field definitions.
Changes:
- Adds
WebSocket Analyticsdataset pages for both account and zone scope. - Adds
BCC,DKIMResult,DMARCPolicy,DMARCResult, andSPFResultto Email Security Alerts. - Adds
ZoneNameto Firewall events. - Adds changelog entry for 2026-06-22.
2 issues need fixing before merge:
- CRITICAL
src/content/changelog/logs/2026-06-22-log-fields-updated.mdx:12— Duplicate "WebSocket Analytics" bullet. Remove the duplicate line. - MEDIUM
src/content/changelog/logs/2026-06-22-log-fields-updated.mdx:2— Title is redundant ("datasets" appears three times). Tighten the title.
No manual edits appear at risk of being overwritten.
| @@ -0,0 +1,19 @@ | |||
| --- | |||
| title: New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs | |||
There was a problem hiding this comment.
Tighten to avoid repeating "datasets":
| title: New Logpush datasets and updated fields across multiple Logpush datasets in Cloudflare Logs | |
| title: New and updated Logpush dataset fields in Cloudflare Logs |
| ### New datasets | ||
|
|
||
| - **WebSocket Analytics**: A new dataset with fields including `BytesReceivedClient`, `BytesReceivedOrigin`, `BytesSentClient`, `BytesSentOrigin`, `ClientASN`, `ClientIP`, `ClientRequestHost`, `ClientRequestPath`, `ClientRequestUserAgent`, `ColoCode`, `ConnectionCloseReason`, `ConnectionCloseSource`, `ConnectionID`, `ConnectionTransportCloseCode`, `EdgeEndTimestamp`, `EdgeStartTimestamp`, and `RayID`. | ||
| - **WebSocket Analytics**: A new dataset with fields including `BytesReceivedClient`, `BytesReceivedOrigin`, `BytesSentClient`, `BytesSentOrigin`, `ClientASN`, `ClientIP`, `ClientRequestHost`, `ClientRequestPath`, `ClientRequestUserAgent`, `ColoCode`, `ConnectionCloseReason`, `ConnectionCloseSource`, `ConnectionID`, `ConnectionTransportCloseCode`, `EdgeEndTimestamp`, `EdgeStartTimestamp`, and `RayID`. |
There was a problem hiding this comment.
Remove this duplicate bullet. WebSocket Analytics is already listed on the preceding line.
|
Review posted on PR #31626. What I did:
Summary of changes:
Issues flagged:
Field descriptions are clear, consistent with existing generated format, and no manual edits appear at risk of being overwritten by future syncs. |
|
Preview URL: https://cc79933e.preview.developers.cloudflare.com Files with changes (up to 15) |
Summary
Automated sync of Logpush dataset field definitions from data/entities.
New datasets
BytesReceivedClient,BytesReceivedOrigin,BytesSentClient,BytesSentOrigin,ClientASN,ClientIP,ClientRequestHost,ClientRequestPath,ClientRequestUserAgent,ColoCode,ConnectionCloseReason,ConnectionCloseSource,ConnectionID,ConnectionTransportCloseCode,EdgeEndTimestamp,EdgeStartTimestamp, andRayID.BytesReceivedClient,BytesReceivedOrigin,BytesSentClient,BytesSentOrigin,ClientASN,ClientIP,ClientRequestHost,ClientRequestPath,ClientRequestUserAgent,ColoCode,ConnectionCloseReason,ConnectionCloseSource,ConnectionID,ConnectionTransportCloseCode,EdgeEndTimestamp,EdgeStartTimestamp, andRayID.Updated fields in existing datasets
BCC,DKIMResult,DMARCPolicy,DMARCResult, andSPFResult.ZoneName.Files changed
src/content/docs/logs/logpush/logpush-job/datasets/account/— dataset pagessrc/content/docs/logs/logpush/logpush-job/datasets/zone/— dataset pagessrc/content/changelog/logs/2026-06-22-log-fields-updated.mdx— changelogDocumentation checklist