Fix getCallerBaggagePairs: resolve userId across all channels#250
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes caller userId OpenTelemetry baggage population in the observability hosting utilities so that user.id is resolved consistently when aadObjectId is missing (e.g., non-Teams channels and A2A scenarios). It aligns the Node implementation with the referenced .NET behavior and adds test coverage for the new precedence rules.
Changes:
- Update
getCallerBaggagePairsto resolveuserIdviaaadObjectId → agenticUserId → from.id. - Add/adjust unit tests to cover non-Teams fallback, A2A fallback, and precedence when all fields are present.
- Add Jest module mapping for
@microsoft/agents-a365-observability-hostingto ensure tests resolve local source.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/observability/extension/hosting/TurnContextUtils.test.ts | Adds coverage for new userId fallback/precedence behavior in caller baggage extraction. |
| tests/observability/extension/hosting/BaggageBuilderUtils.test.ts | Updates expectation to reflect new caller userId baggage population via fallback chain. |
| tests/jest.config.cjs | Adds moduleNameMapper entry so tests can import @microsoft/agents-a365-observability-hosting from workspace source. |
| packages/agents-a365-observability-hosting/src/utils/TurnContextUtils.ts | Implements userId fallback chain when building caller baggage pairs. |
userId was only set from aadObjectId, which is undefined on non-Teams channels and A2A calls. Add fallback chain: aadObjectId → agenticUserId → from.id Port of microsoft/Agent365-dotnet#246 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
feb3b9f to
71ff10d
Compare
juliomenendez
approved these changes
May 5, 2026
alexlu4250
approved these changes
May 5, 2026
alexlu4250
reviewed
May 5, 2026
alexlu4250
approved these changes
May 5, 2026
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
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.
Summary
aadObjectId, which isundefinedon non-Teams channels and A2A callsaadObjectId → agenticUserId → from.idChannel behavior after fix
Test plan
🤖 Generated with Claude Code