Codex emits seven OpenTelemetry metrics — and AWS documents the sidecar that captures them

AWS Machine Learning Blog·medium signalXBlueskyLinkedInCopy link

An August 6 AWS post enumerates the telemetry Codex actually emits: `codex.api_request`, `codex.api_request.duration_ms`, `codex.turn.e2e_duration_ms`, `codex.turn.token_usage`, `codex.turn.tool.call`, `codex.thread.started`, and `codex.conversation.turn.count`. The pattern runs a collector on each developer workstation listening only on `127.0.0.1:4318/v1/metrics`, enriching with org context and signing to CloudWatch with SigV4 — deliberately keeping any centralized proxy out of the model-request path. Caveat worth flagging: the post says it documents a public guidance repository and "does not imply publication or endorsement by AWS," and does not confirm official Codex availability on Bedrock.