---
title: New WebSocket Analytics Logpush dataset
description: Push per-connection WebSocket close reason, close source, and session metadata to any Logpush destination.
image: https://edgetunnel-b2h.pages.dev/changelog-preview.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://edgetunnel-b2h.pages.dev/changelog/) 

## New WebSocket Analytics Logpush dataset

Jul 07, 2026 

[ Logs ](https://edgetunnel-b2h.pages.dev/logs/) 

Enterprise customers can now push per-connection WebSocket analytics to any [Logpush destination](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/enable-destinations/) using the new `websocket_analytics` dataset. Each log record is emitted when a WebSocket connection closes and includes fields that were previously only available to Cloudflare engineers via internal tooling.

Key fields include:

* **`ConnectionCloseReason`** — why the connection ended: `peerReset`, `peerNoError`, `timedOut`, `upstreamReset`, `protocolViolation`, `unspecifiedError`, or `none`.
* **`ConnectionCloseSource`** — which side initiated the close: `upstream`, `downstream`, `me`, or `both`.
* **`ConnectionTransportCloseCode`** — the TLS alert code or TCP-level close code for additional precision.
* **`RayID`** — correlate WebSocket connection events with your existing HTTP Request logs.

The dataset also includes directional byte counts (`BytesSentClient`, `BytesReceivedClient`, `BytesSentOrigin`, `BytesReceivedOrigin`), connection timestamps, client IP, colo code, and request metadata from the original WebSocket upgrade.

This data lets you build alerts on connection close patterns — for example, detecting spikes in TCP resets (`ConnectionCloseReason == "peerReset"`) grouped by host and data center — directly in your existing log analysis tools.

For the full list of available fields, refer to [WebSocket Analytics](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/datasets/zone/websocket%5Fanalytics/).

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-07-websocket-analytics-dataset/#page","headline":"New WebSocket Analytics Logpush dataset · Changelog","description":"Push per-connection WebSocket close reason, close source, and session metadata to any Logpush destination.","url":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-07-websocket-analytics-dataset/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/changelog-preview.png","dateModified":"2026-07-07","datePublished":"2026-07-07","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```