-
Notifications
You must be signed in to change notification settings - Fork 15.3k
[Logs] Update Logpush dataset field definitions (2026-06-09) #31335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+238
−0
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
14 changes: 14 additions & 0 deletions
14
src/content/changelog/logs/2026-06-09-log-fields-updated.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,14 @@ | ||||||
| --- | ||||||
| title: New Logpush datasets in Cloudflare Logs | ||||||
| description: New Logpush datasets are now available in Cloudflare Logs. | ||||||
| date: 2026-06-09 | ||||||
| --- | ||||||
|
|
||||||
| Cloudflare has updated [Logpush datasets](/logs/logpush/logpush-job/datasets/): | ||||||
|
|
||||||
| ### 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`. | ||||||
|
|
||||||
|
Comment on lines
+12
to
+13
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove the duplicate. WebSocket Analytics is a single dataset available in both account and zone scopes.
Suggested change
|
||||||
| For the complete field definitions for each dataset, refer to [Logpush datasets](/logs/logpush/logpush-job/datasets/). | ||||||
112 changes: 112 additions & 0 deletions
112
src/content/docs/logs/logpush/logpush-job/datasets/account/websocket_analytics.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,112 @@ | ||
| --- | ||
| # Code generator. DO NOT EDIT. | ||
|
|
||
| title: WebSocket Analytics | ||
| pcx_content_type: configuration | ||
| sidebar: | ||
| order: 21 | ||
| --- | ||
|
|
||
| The descriptions below detail the fields available for `websocket_analytics`. | ||
|
|
||
| ## BytesReceivedClient | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes received from the client. | ||
|
|
||
| ## BytesReceivedOrigin | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes received from the origin. | ||
|
|
||
| ## BytesSentClient | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes sent to the client. | ||
|
|
||
| ## BytesSentOrigin | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes sent to the origin. | ||
|
|
||
| ## ClientASN | ||
|
|
||
| Type: `int` | ||
|
|
||
| The client's autonomous system number (ASN). | ||
|
|
||
| ## ClientIP | ||
|
|
||
| Type: `string` | ||
|
|
||
| The client IP address. | ||
|
|
||
| ## ClientRequestHost | ||
|
|
||
| Type: `string` | ||
|
|
||
| The host requested by the client in the WebSocket upgrade request. | ||
|
|
||
| ## ClientRequestPath | ||
|
|
||
| Type: `string` | ||
|
|
||
| The path requested by the client in the WebSocket upgrade request. | ||
|
|
||
| ## ClientRequestUserAgent | ||
|
|
||
| Type: `string` | ||
|
|
||
| The user agent reported by the client. | ||
|
|
||
| ## ColoCode | ||
|
|
||
| Type: `string` | ||
|
|
||
| IATA airport code of the data center that handled the connection. | ||
|
|
||
| ## ConnectionCloseReason | ||
|
|
||
| Type: `string` | ||
|
|
||
| The reason the WebSocket connection ended. Possible values are <em>none</em> \| <em>unspecifiedError</em> \| <em>timedOut</em> \| <em>peerReset</em> \| <em>upstreamReset</em> \| <em>protocolViolation</em> \| <em>peerNoError</em>. | ||
|
|
||
| ## ConnectionCloseSource | ||
|
|
||
| Type: `string` | ||
|
|
||
| Which side initiated the connection close; <em>upstream</em> \| <em>downstream</em> \| <em>me</em> \| <em>both</em>, or the raw internal value if unrecognized. | ||
|
|
||
| ## ConnectionID | ||
|
|
||
| Type: `string` | ||
|
|
||
| Unique identifier of the WebSocket connection, hex-encoded. | ||
|
|
||
| ## ConnectionTransportCloseCode | ||
|
|
||
| Type: `int` | ||
|
|
||
| The first transport-level close code observed. For TLS connections this is the TLS alert code; for plain TCP connections (no TLS) it is always 0. The most significant bit indicates the source: 0 = proxy-initiated, 1 = eyeball-initiated. | ||
|
|
||
| ## EdgeEndTimestamp | ||
|
|
||
| Type: `int or string` | ||
|
|
||
| Timestamp at which the WebSocket connection closed. | ||
|
|
||
| ## EdgeStartTimestamp | ||
|
|
||
| Type: `int or string` | ||
|
|
||
| Timestamp at which the WebSocket connection was established. | ||
|
|
||
| ## RayID | ||
|
|
||
| Type: `string` | ||
|
|
||
| The Ray ID of the WebSocket upgrade request. |
112 changes: 112 additions & 0 deletions
112
src/content/docs/logs/logpush/logpush-job/datasets/zone/websocket_analytics.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,112 @@ | ||
| --- | ||
| # Code generator. DO NOT EDIT. | ||
|
|
||
| title: WebSocket Analytics | ||
| pcx_content_type: configuration | ||
| sidebar: | ||
| order: 21 | ||
| --- | ||
|
|
||
| The descriptions below detail the fields available for `websocket_analytics`. | ||
|
|
||
| ## BytesReceivedClient | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes received from the client. | ||
|
|
||
| ## BytesReceivedOrigin | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes received from the origin. | ||
|
|
||
| ## BytesSentClient | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes sent to the client. | ||
|
|
||
| ## BytesSentOrigin | ||
|
|
||
| Type: `int` | ||
|
|
||
| Number of bytes sent to the origin. | ||
|
|
||
| ## ClientASN | ||
|
|
||
| Type: `int` | ||
|
|
||
| The client's autonomous system number (ASN). | ||
|
|
||
| ## ClientIP | ||
|
|
||
| Type: `string` | ||
|
|
||
| The client IP address. | ||
|
|
||
| ## ClientRequestHost | ||
|
|
||
| Type: `string` | ||
|
|
||
| The host requested by the client in the WebSocket upgrade request. | ||
|
|
||
| ## ClientRequestPath | ||
|
|
||
| Type: `string` | ||
|
|
||
| The path requested by the client in the WebSocket upgrade request. | ||
|
|
||
| ## ClientRequestUserAgent | ||
|
|
||
| Type: `string` | ||
|
|
||
| The user agent reported by the client. | ||
|
|
||
| ## ColoCode | ||
|
|
||
| Type: `string` | ||
|
|
||
| IATA airport code of the data center that handled the connection. | ||
|
|
||
| ## ConnectionCloseReason | ||
|
|
||
| Type: `string` | ||
|
|
||
| The reason the WebSocket connection ended. Possible values are <em>none</em> \| <em>unspecifiedError</em> \| <em>timedOut</em> \| <em>peerReset</em> \| <em>upstreamReset</em> \| <em>protocolViolation</em> \| <em>peerNoError</em>. | ||
|
|
||
| ## ConnectionCloseSource | ||
|
|
||
| Type: `string` | ||
|
|
||
| Which side initiated the connection close; <em>upstream</em> \| <em>downstream</em> \| <em>me</em> \| <em>both</em>, or the raw internal value if unrecognized. | ||
|
|
||
| ## ConnectionID | ||
|
|
||
| Type: `string` | ||
|
|
||
| Unique identifier of the WebSocket connection, hex-encoded. | ||
|
|
||
| ## ConnectionTransportCloseCode | ||
|
|
||
| Type: `int` | ||
|
|
||
| The first transport-level close code observed. For TLS connections this is the TLS alert code; for plain TCP connections (no TLS) it is always 0. The most significant bit indicates the source: 0 = proxy-initiated, 1 = eyeball-initiated. | ||
|
|
||
| ## EdgeEndTimestamp | ||
|
|
||
| Type: `int or string` | ||
|
|
||
| Timestamp at which the WebSocket connection closed. | ||
|
|
||
| ## EdgeStartTimestamp | ||
|
|
||
| Type: `int or string` | ||
|
|
||
| Timestamp at which the WebSocket connection was established. | ||
|
|
||
| ## RayID | ||
|
|
||
| Type: `string` | ||
|
|
||
| The Ray ID of the WebSocket upgrade request. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove duplicate entry. The WebSocket Analytics dataset is listed twice; since this is a single dataset available in both account and zone scopes, it should only appear once in the changelog.
BytesReceivedClientBytesReceivedOriginBytesSentClientBytesSentOriginClientASNClientIPClientRequestHostClientRequestPathClientRequestUserAgentColoCodeConnectionCloseReasonConnectionCloseSourceConnectionIDConnectionTransportCloseCodeEdgeEndTimestampEdgeStartTimestampRayID