You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add TelemetryConfig to all four SDKs (Node, Python, Go, .NET) to configure
OpenTelemetry instrumentation on the Copilot CLI process. This includes:
- TelemetryConfig type with OTLP endpoint, file exporter, source name, and
capture-content options, mapped to CLI environment variables
- W3C Trace Context propagation (traceparent/tracestate) on session.create,
session.resume, and session.send RPC calls
- Trace context restoration in tool call handlers (v2 RPC and v3 broadcast)
so user tool code executes within the correct distributed trace
- Telemetry helper modules (telemetry.ts, telemetry.py, telemetry.go,
Telemetry.cs) with unit tests
- Updated generated types from latest schema
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Trace context (`traceparent`/`tracestate`) is automatically propagated between the SDK and CLI on `CreateSession`, `ResumeSession`, and `Send` calls, and inbound when the CLI invokes tool handlers.
497
497
498
+
> **Note:** The current `ToolHandler` signature does not accept a `context.Context`, so the inbound trace context cannot be passed to handler code. Spans created inside a tool handler will not be automatically parented to the CLI's `execute_tool` span. A future version may add a context parameter.
0 commit comments