[otel] exporter receiving resourceSpans with h2 internals instead of resourceLogs with codex.* events

[Credgate]

Trying to get the documented OTEL telemetry working and my config matches the docs:

toml[otel]
environment = "prod"
log_user_prompt = false

[otel.exporter."otlp-grpc"]
endpoint = "https://your-otel-collector:4317"

[otel.exporter."otlp-grpc".headers]
"x-api-key" = "your-api-key"

Based on the observability docs I'd expect to see resourceLogs containing events like codex.api_request, codex.tool_result, codex.conversation_starts etc.
What I'm actually getting is resourceSpans containing only low-level h2 HTTP/2 transport spans things like Prioritize::queue_frame, FramedWrite::flush, hpack::encode with no codex.* events anywhere in the payload.

A few questions:
Is resourceSpans the expected output format or should this be resourceLogs?
Are the codex.* log events documented on the config-advanced page actually emitted yet in this version 0.119.0-alpha.28?
Is there a separate config needed to enable the log pipeline vs the trace pipeline?

EDIT: When switching to HTTP JSON format i do get the codex.* events i'd expect but i'd much prefer to use GRPC.

EDIT2: Thinking this is a bug where the h2 noise i'm seeing looks like it's Codex's gRPC connection to the OpenAI API being captured by the unfiltered tracing subscriber and then exported over my gRPC OTEL connection. I'm guessing both use the same h2 library, so the subscriber can't distinguish between "this is the app's API call" and "this is the OTEL export call." 🤷

[agammann]

For 0.119.0-alpha.28, there is a configuration detail that explains why you can receive spans even though you only configured otel.exporter: when trace_exporter is omitted, that version copies exporter into it. See the configuration loader at that release.

To keep gRPC log export while disabling the extra trace pipeline, add trace_exporter = "none" directly under [otel], before the nested exporter table:

[otel]
environment = "prod"
log_user_prompt = false
trace_exporter = "none"

[otel.exporter."otlp-grpc"]
endpoint = "https://your-otel-collector:4317"

[otel.exporter."otlp-grpc".headers]
"x-api-key" = "your-api-key"

Keep your actual collector endpoint/authentication settings in place. Restart Codex after changing the configuration.

The two signals are separate in that release:

• otel.exporter constructs a LogExporter, including for gRPC; its decoded OTLP payload should contain resourceLogs. See the gRPC logger construction.
• otel.trace_exporter constructs a SpanExporter, which produces the trace signal (resourceSpans). Its filter admits every span via meta.is_span(), so the h2 span noise is consistent with this enabled trace pipeline. See the trace filter.

Disabling trace export isolates that noise; it does not by itself prove why your gRPC logs are missing. If logs are still absent, check that the collector accepts opentelemetry.proto.collector.logs.v1.LogsService/Export and routes its OTLP receiver into a logs pipeline, rather than inspecting only its traces output. Your HTTP/JSON result already demonstrates that the expected events are being generated in your run.

This is source-based analysis of your exact release, not an end-to-end reproduction against your collector. AI-assisted answer (Codex).