.Net: Added traces for Agent invocations#10387
Merged
dmytrostruk merged 9 commits intomicrosoft:mainfrom Feb 4, 2025
Merged
Conversation
markwallace-microsoft
added
.NET
dmytrostruk
temporarily deployed
to
integration
GitHub Actions
Inactive
dmytrostruk
temporarily deployed
to
integration
GitHub Actions
Inactive
westey-m
approved these changes
Feb 4, 2025
dmytrostruk
temporarily deployed
to
integration
GitHub Actions
Inactive
markwallace-microsoft
approved these changes
Feb 4, 2025
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
TaoChenOSU
approved these changes
Feb 4, 2025
crickman
approved these changes
Feb 4, 2025
4 tasks
markwallace-microsoft
added
the
kernel
dmytrostruk
temporarily deployed
to
integration
GitHub Actions
Inactive
crickman
approved these changes
Feb 4, 2025
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Feb 5, 2025
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Python parity with this PR: #10387 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Update agent invoke span name and add attributes. This is a breaking change: users who are currently relying on the span name in their queries will need to update their queries to use the new name or match new patterns. This is an experimental feature so breaking changes are expected. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄
jcruzmot-te
pushed a commit
to thousandeyes/aia-semantic-kernel
that referenced
this pull request
Sep 15, 2025
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Resolves: microsoft#10174 This PR instruments Agent invocation operation with traces and adds an example with tracing enabled using Console and Application Insights. Trace operation and attribute names are based on the work in following PR about adding AI Agent Semantic Convention to OpenTelemetry (currently in-progress): open-telemetry/semantic-conventions#1739. Examples from Application Insights: End-to-end transaction:  Traces:  Trace attributes related to Agent:  ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone 😄
jcruzmot-te
pushed a commit
to thousandeyes/aia-semantic-kernel
that referenced
this pull request
Sep 15, 2025
### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Python parity with this PR: microsoft#10387 ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> Update agent invoke span name and add attributes. This is a breaking change: users who are currently relying on the span name in their queries will need to update their queries to use the new name or match new patterns. This is an experimental feature so breaking changes are expected. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄
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
5 participants
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.
Motivation and Context
Resolves: #10174
This PR instruments Agent invocation operation with traces and adds an example with tracing enabled using Console and Application Insights.
Trace operation and attribute names are based on the work in following PR about adding AI Agent Semantic Convention to OpenTelemetry (currently in-progress): open-telemetry/semantic-conventions#1739.
Examples from Application Insights:
End-to-end transaction:
Traces:
Trace attributes related to Agent:
Contribution Checklist