Skip to content

Add limitation for websocket logging #24358

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 12, 2025
Merged

Add limitation for websocket logging #24358

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f51c2b1
Add limitation for websocket logging
kodster28 Aug 12, 2025
bd02415
Update src/content/docs/workers/observability/logs/real-time-logs.mdx
kodster28 Aug 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions src/content/docs/workers/observability/logs/real-time-logs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,12 +83,11 @@ You can filter real-time logs in the dashboard or using [`wrangler tail`](/worke

:::

Note that:

- Real-time logs does not store Workers Logs. To store logs, use [Workers Logs](/workers/observability/logs/workers-logs).
- If your Worker has a high volume of traffic, the real-time logs might enter sampling mode. This will cause some of your messages to be dropped and a warning to appear in your logs.
- Logs from any [Durable Objects](/durable-objects/) your Worker is using will show up in the dashboard.
- A maximum of 10 clients can view a Worker's logs at one time. This can be a combination of either dashboard sessions or `wrangler tail` calls.
- When using `wrangler tail` with [WebSocket event handlers](/workers/runtime-apis/websockets/), any `console.log` statements within those handlers are hidden under the WebSocket client closes the connection. Once the `close` is received, all messages are flushed, printing everything to the terminal at once.

## Persist logs

Expand Down