Add A365 telemetry correlation for WebSocket invocations

[Yulin Li (yulin-li)]

Description

invocations_ws previously excluded WebSocket scopes from W3C trace propagation and did not attach the Agent 365 session baggage used to enrich spans created by customer handler code. This aligns WebSocket telemetry with the existing REST invocations behavior.

The change propagates incoming traceparent, tracestate, and baggage through the WebSocket lifecycle; attaches the canonical azure.ai.agentserver.session_id; and maps that context onto exported child spans and close-event logs. REST and WebSocket now share the existing core session key instead of defining protocol-specific duplicates.

Customer-code coverage creates and exports an explicit customer.websocket.process_message span, verifying its remote parent, instrumentation scope, custom attributes, A365 session correlation, and Foundry project identity. A hosted dual-protocol E2E run also confirmed the customer-created invocations_ws_a365_e2e span in Application Insights with session, agent, blueprint, and project enrichment.

The shared microsoft-opentelemetry optional OpenAI Agents instrumentation warning (ModuleNotFoundError: agents) reproduces for both REST and WebSocket and is intentionally unchanged.

Validation:

• Invocations test suite: 190 passed, 2 skipped
• Package pylint and pyright checks passed
• Hosted Agent 365 E2E marker: customer-ws-span-20260711T153708Z

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Pull request overview

Aligns WebSocket telemetry with REST invocation tracing and Agent 365 correlation.

Changes:

• Propagates W3C context through WebSocket connections.
• Adds canonical session baggage to handler spans and close logs.
• Adds tracing tests and updates documentation.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
core/CHANGELOG.md	Records WebSocket propagation support.
core/_base.py	Documents WebSocket middleware behavior.
core/_tracing.py	Enables context extraction for WebSockets.
invocations/CHANGELOG.md	Records Agent 365 correlation.
invocations/README.md	Updates WebSocket telemetry documentation.
invocations/_constants.py	Removes protocol-specific session key.
invocations/_invocation.py	Reuses the shared baggage constant.
invocations/_invocation_ws.py	Attaches session baggage throughout connections.
tests/conftest.py	Updates close-log filtering.
tests/test_ws_close_event.py	Checks the canonical session field.
tests/test_ws_session_id.py	Updates session-log assertions.
tests/test_ws_tracing.py	Tests baggage, parenting, and enrichment.

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

sdk/agentserver/azure-ai-agentserver-invocations/azure/ai/agentserver/invocations/_invocation_ws.py:398

• This replaces the previously documented azure.ai.agentserver.invocations_ws.session_id close-event field rather than adding the shared key alongside it. Existing structured-log queries and processors will therefore lose session correlation, which contradicts the PR's “no breaking changes” declaration (the old field is documented in the 1.0.0b4 changelog). Preserve compatibility by emitting both keys for a transition period, or explicitly classify and document the schema change as breaking.

            _BAGGAGE_SESSION_ID: session_id,

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

sdk/agentserver/azure-ai-agentserver-core/azure/ai/agentserver/core/_tracing.py:485

• WebSocket upgrade requests may carry baggage or tracestate across multiple header fields, but the dict carrier below retains only the last value. With this scope now enabled, earlier caller baggage entries are silently dropped instead of being propagated. Combine repeated header values (comma-separated, as required by W3C list headers) before calling extract; normalizing names also avoids relying on the ASGI server to lowercase them.

        if scope["type"] not in ("http", "websocket"):

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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

Suppressed comments (1)

sdk/agentserver/azure-ai-agentserver-invocations/azure/ai/agentserver/invocations/_invocation_ws.py:404

• Replacing the structured close-event field removes the azure.ai.agentserver.invocations_ws.session_id contract documented for the stable 1.0.0 release (CHANGELOG.md:77). Existing dashboards and log queries will stop correlating sessions after a patch upgrade, despite this PR declaring no breaking changes. Emit both the legacy and canonical keys for a deprecation window, or treat the removal as a breaking release.

            _BAGGAGE_SESSION_ID: session_id,

[Copilot]

Pull request overview

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

[Copilot]

Pull request overview

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