fix(otel): stop sending traces to api.openai.com and cleanup

[krisztianfekete]

The Agents SDK registers a trace processor that POSTs everything to a hardcoded https://api.openai.com/v1/traces/ingest using OPENAI_API_KEY. It ignores OPENAI_API_BASE, so anyone behind other proxies is shipping their gateway's key to OpenAI and getting 401s back.

OpenAIAgentsInstrumentor adds the OTel processor next to that one rather than replacing it, and set_tracing_disabled(True) would silence the OTel spans too, so we now drop the built-in processor before instrumenting. Set KAGENT_OPENAI_AGENTS_NATIVE_TRACING=true to keep it if you're using a real OpenAI key.

Using OpenAIAgentsInstrumentor(replace_existing_processors=True) as suggested in review, with the pin bumped to >=0.52.3,<0.53.0 since that's when the kwarg landed. Doing it through the kwarg also means a second build() can't wipe the OTel processor, since instrument() no-ops once instrumented.

Cleaned up a couple of other smaller stuff:

• Resource(...) -> Resource.create(...): the bare constructor ignores OTEL_RESOURCE_ATTRIBUTES and drops telemetry.sdk.*, so nobody could set deployment.environment.name or service.version at all.
• Same bug in the Go ADK, resource.New starts empty so it needs WithFromEnv() + WithTelemetrySDK().
• HTTPXClientInstrumentor().instrument(excluded_urls=...) did nothing, cleaned it up.
• _a2a.py read self.config.kagent_url but KAgentConfig only has url, which blows up whenever KAGENT_URL isn't set.

Rebased onto main, which dropped the Gemini bullet from this PR since main landed the same fix independently.

[Copilot]

Pull request overview

This PR hardens and cleans up OpenTelemetry integration around the OpenAI Agents SDK runtime to prevent unintended trace export to OpenAI’s hardcoded ingest endpoint (which can leak non-OpenAI gateway keys and cause 401s), while preserving OpenTelemetry-based tracing.

Changes:

• Drop the OpenAI Agents SDK native trace processor by default (opt-in via KAGENT_OPENAI_AGENTS_NATIVE_TRACING=true) and instrument the SDK via OpenAIAgentsInstrumentor.
• Ensure Resource.create(...) is used so OTEL_RESOURCE_ATTRIBUTES and telemetry.sdk.* attributes are honored.
• Ensure Gemini instrumentation still runs when OTEL_LOGGING_ENABLED=true, and remove a no-op excluded_urls argument from HTTPXClientInstrumentor().instrument(...).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
python/packages/kagent-openai/tests/test_tracing.py	Adds regression tests proving the Agents SDK default exporter targets OpenAI, and that kagent drops it by default while keeping OTel spans working.
python/packages/kagent-openai/src/kagent/openai/_a2a.py	Introduces _configure_openai_agents_tracing() to remove native exporting (by default) and warn when SDK tracing is disabled, then wires it into app startup.
python/packages/kagent-core/tests/test_tracing_configure.py	Adds tests ensuring Google/Gemini instrumentation still runs in the logging-only branch and that OTEL_RESOURCE_ATTRIBUTES are merged into the Resource.
python/packages/kagent-core/src/kagent/core/tracing/_utils.py	Switches to Resource.create(...), removes ineffective excluded_urls for HTTPX instrumentor, and ensures Google/Gemini instrumentation also runs when logging is enabled.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dhaifley]

Looks good, but what if we just used the newer version mentioned in the PR description? >=0.52.3,<0.53.0? I'm not familiar enough to know if there is a reason we cannot do that.

Also, does the Go ADK code need a similar fix: go/adk/pkg/telemetry/tracing.go:81-84?

[krisztianfekete]

Thanks @dhaifley, addressed your comments and fixed a new bug with KAgentConfig. Didn't want to upgrade originally, as hopefully shortly we're moving away from the Traceloop libraries, but couldn't find dangerous changes, so went with it this time.