[PratikDhanave (PratikDhanave)]

Go has otelprovider (an OpenTelemetry tracing middleware) but examples/ has no sample, unlike the .NET AgentOpenTelemetry sample.

Change

• New examples/02-agents/observability/step01_agent_tracing that installs a stdout OpenTelemetry tracer (stdouttrace, already a dependency) as the global provider and wraps a Foundry agent with otelprovider.NewMiddleware, so the run emits a gen_ai invoke_agent span (model, usage, finish reason) printed to stdout.
• Registered in cmd/verifyexamples (env-gated on FOUNDRY_PROJECT_ENDPOINT).

Builds, go vet, gofumpt clean; no go.mod changes; the verifyexamples test passes.

[Copilot]

Copilot review overview

🟡 Changes recommended

The example description claims a model attribute that the middleware does not emit.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Align sample span model claim with middleware instrumentation · New

What changed in this PR

Adds an OpenTelemetry tracing example for Foundry agents and registers it with verifyexamples.

Changes:

• Exports agent spans to stdout.
• Registers environment-gated example verification.

File	Description
examples/​02-agents/​observability/​step01_agent_tracing/​main.go	New agent tracing sample
cmd/​verifyexamples/​examples.go	Registers the sample for verification

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

API consistency review

Result	Scope
aligned	examples

Changed Go contract

None to exported APIs. Adds the sample examples/02-agents/observability/step01_agent_tracing, which wraps a Foundry agent with otelprovider.NewMiddleware. The sample is registered in cmd/verifyexamples.

Upstream evidence reviewed

Implementation	Source	Contract checked
.NET	dotnet/samples/02-agents/AgentOpenTelemetry	Agent tracing sample exists upstream
Python	python/samples/02-agents/observability/ (agent_observability.py, foundry_agent_tracing.py)	Observability sample folder with agent tracing exists upstream

Assessment

Both upstream SDKs have an agent tracing sample, and the Go sample covers the same scenario. It is placed under a matching observability folder. No exported API or default changed, so there are no parity issues. I only compared the sample folders and names. I did not read upstream sample contents, because the code search API was rate-limited. public-api-change is not applicable.

Generated by Go API Consistency Review Agent · copilot · auto · 17.3 AIC · ⌖ 0.616 AIC · ⊞ 5.1K · ◷