channel should flow to all scopes - #70
Conversation
There was a problem hiding this comment.
Pull request overview
This PR restructures the propagation of channel-related execution context attributes to flow to all span scopes instead of being limited to invoke-agent operations. Two constants (GEN_AI_EXECUTION_SOURCE_NAME_KEY and GEN_AI_EXECUTION_SOURCE_DESCRIPTION_KEY) are moved from INVOKE_AGENT_ATTRIBUTES to COMMON_ATTRIBUTES, ensuring channel information is captured across all telemetry scopes.
Key Changes
- Channel source metadata attributes (
gen_ai.channel.nameandgen_ai.channel.link) are now propagated to all spans, not just invoke-agent spans - The "Execution context" comment grouping is moved with these attributes to maintain logical organization
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
…gents_a365/observability/core/trace_processor/util.py Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
Task
channel info should be propagated to all tables