fix(runtime): add OpenTelemetry tracer to runtime initialization#2505
Open
tdabasinskas wants to merge 1 commit intodocker:mainfrom
Open
fix(runtime): add OpenTelemetry tracer to runtime initialization#2505tdabasinskas wants to merge 1 commit intodocker:mainfrom
tdabasinskas wants to merge 1 commit intodocker:mainfrom
Conversation
Initialize runtime instances with an OpenTelemetry tracer named "cagent" to enable distributed tracing across agent invocations. This ensures consistent tracing instrumentation in: - Agent-to-agent adapter runtime - MCP server tool handler runtime - Session manager runtime
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
1 participant
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.
Wire an OpenTelemetry tracer into the runtime instances created by the non-interactive entry points so they emit spans like the CLI already does:
Without this,
LocalRuntime.startSpanseesr.tracer == niland silently returns a noop, so users running in MCP, API or A2A mode withOTEL_EXPORTER_OTLP_ENDPOINTset get an initialized SDK that never emits anything.It uses the same
"cagent"scope ascmd/root/run.gofor consistency. No behavior change when OTel is disabled — the global tracer provider is a noop untilinitOTelSDKruns.