jif 91e6da943b Stop logging every Responses WebSocket event (#29432) ...

## 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.

91e6da943b · 2026-06-22 17:43:08 +02:00

History

..

events

Stop logging every Responses WebSocket event (#29432)

2026-06-22 17:43:08 +02:00

metrics

[codex] Add second-based OTEL duration histograms (#27058)

2026-06-15 17:10:52 -07:00

config.rs

codex-otel: add configurable trace metadata (#21556)

2026-05-07 16:06:57 -07:00

lib.rs

feat: add Bedrock API key as a managed auth mode (#27443)

2026-06-10 20:42:38 -07:00

otlp.rs

fix(otel): make HTTP trace export survive app-server runtimes (#14300)

2026-03-11 12:33:10 -07:00

provider.rs

codex-otel: validate provider span attributes consistently (#21749)

2026-05-08 08:20:49 -07:00

targets.rs

chore(otel): reorganize codex-otel crate (#13800)

2026-03-06 14:58:18 -08:00

trace_context.rs

codex-otel: add configurable trace metadata (#21556)

2026-05-07 16:06:57 -07:00