Stop logging every Responses WebSocket event#29432
Merged
Merged
Conversation
rodolphoeck-oai
approved these changes
Jun 22, 2026
|
Thanks for approving these so fast - crossing fingers it lands in the next release. |
|
please ~ |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
Every successful Responses WebSocket event currently produces three local log records: the full payload at TRACE, an OpenTelemetry log event, and an OpenTelemetry trace event.
On busy threads these records fill the 1,000-row log partition in seconds and cause continuous SQLite insert-and-prune churn.
Related to https://openai.slack.com/archives/C095U48JNL9/p1782128972644209
What changed
codex.websocket_eventas OpenTelemetry log and trace events.