Add installed Claude and Codex tracing journeys - #739
Merged
Merged
Conversation
tt-le
requested review from
AarushiShah-db,
lilly-luo and
rohita5l
as code owners
September 18, 2026 14:17
tt-le
force-pushed
the
tien/codex-otel-tracing-integration
branch
from
September 18, 2026 14:20
e47cf08 to
7f8a34b
Compare
An error occurred while trying to automatically change base from
tien/codex-otel-gateway-proxy
to
tien/gateway-proxy-parameterize
September 18, 2026 14:53
tt-le
changed the title
tt-le
force-pushed
the
tien/codex-otel-tracing-integration
branch
from
September 22, 2026 22:00
89449cd to
b15d7af
Compare
tt-le
force-pushed
the
tien/codex-otel-tracing-integration
branch
from
September 22, 2026 22:02
b15d7af to
faa58b4
Compare
Point the tracing journey at the CI trace table main.aigw_tracing.unity_gateway_otel_spans and assert the marker span also carries Codex's `model` attribute, so the trace is attributable to the model that actually ran. Co-authored-by: Isaac <no-reply@databricks.com>
tt-le
force-pushed
the
tien/codex-otel-tracing-integration
branch
from
September 22, 2026 23:17
288db31 to
881da93
Compare
andy-xu-db
approved these changes
Sep 23, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What & why
Add installed-product customer journeys for the Claude Code and Codex tracing paths now on
main:The workspace deliberately has no published CodingAgentConfig, so these journeys use the integration suite's managed-config stub seam for only that configuration input. The agents, inference, OTLP export, SQL warehouse, and table verification remain real.
Claude Code sends traces directly to the gateway and obtains the current bearer through its
otelHeadersHelper; the journey correlates those spans withOTEL_RESOURCE_ATTRIBUTESand verifiesgen_ai.request.model. Codex sends credential-free OTLP requests to its loopback proxy, which injects the current Databricks token only on the upstream trace request; its marker uses Codex's supportedotel.span_attributesconfiguration. Inference traffic does not use the Codex proxy.Both journeys run only in the existing Full lane for their agent and reuse the eng-ml inference workspace and bearer. During setup they get the workspace ID from an authenticated response, read the effective tracing config, and derive the configured
<catalog>.<schema>.<prefix>_otel_spanstable; the workflow and runner do not carry a hardcoded table name.Testing
DATABRICKS_BEARERlacksUSE SCHEMAon the configured tracing schema; the test intentionally remains strict rather than skipping table verification.This pull request and its description were written by Isaac.