[Monitor OpenTelemetry Exporter] Add Support for User Semantic Conventions #35790
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.
Packages impacted by this PR
@azure/monitor-opentelemetry-exporter
Describe the problem that is addressed by this PR
https://msazure.visualstudio.com/One/_git/CommonSchema/pullrequest/13225763?path=/v4.0/Mappings/AzureMonitor-AI.md
This pull request updates how OpenTelemetry end user identifiers are mapped to Application Insights tags, ensuring more accurate user tracking and improved compatibility with semantic conventions. The main changes involve introducing support for new experimental OpenTelemetry attributes, updating mapping logic, and enhancing test coverage.
End User Attribute Mapping:
ATTR_ENDUSER_ID
andATTR_ENDUSER_PSEUDO_ID
inexperimentalOpenTelemetryValues
, and included them inhttpSemanticValues
for consistent attribute handling. [1] [2]createTagsFromSpan
andcreateTagsFromLog
to mapATTR_ENDUSER_ID
toai.user.authUserId
andATTR_ENDUSER_PSEUDO_ID
toai.user.id
, replacing the previous usage ofSEMATTRS_ENDUSER_ID
. [1] [2]Codebase Cleanup:
SEMATTRS_ENDUSER_ID
throughout the codebase, switching to the new experimental attributes for user identification. [1] [2] [3]Testing Improvements:
ATTR_ENDUSER_ID
andATTR_ENDUSER_PSEUDO_ID
to Application Insights tags, and to ensure these attributes are not included in properties. [1] [2] [3] [4]Are there test cases added in this PR? (If not, why?)
Yes
Checklists