Skip to content

Stop logging every Responses WebSocket event#29432

Merged
jif-oai merged 1 commit into
mainfrom
jif/stop-persisting-websocket-events
Jun 22, 2026
Merged

Stop logging every Responses WebSocket event#29432
jif-oai merged 1 commit into
mainfrom
jif/stop-persisting-websocket-events

Conversation

@jif-oai

@jif-oai jif-oai commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

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

  • Stop logging each successful Responses WebSocket payload at TRACE.
  • Stop emitting codex.websocket_event as OpenTelemetry log and trace events.
  • Keep WebSocket event counters, duration metrics, response timing metrics, parsing, and error handling.

@Allmight97

Copy link
Copy Markdown

Thanks for approving these so fast - crossing fingers it lands in the next release.

@ahmermalik

Copy link
Copy Markdown

please ~

@1996fanrui 1996fanrui left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the fix

@jif-oai jif-oai merged commit 91e6da9 into main Jun 22, 2026
31 checks passed
@jif-oai jif-oai deleted the jif/stop-persisting-websocket-events branch June 22, 2026 15:43
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 22, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants