Add OpenTelemetry app diagnostics - #515
Merged
heyitsaamir merged 2 commits intoJul 22, 2026
Merged
Conversation
This was referenced Jul 20, 2026
heyitsaamir
force-pushed
the
heyitsaamir-python-otel-apps
branch
from
July 22, 2026 14:27
b8f9702 to
18a5d99
Compare
Base automatically changed from
heyitsaamir-python-otel-api
to
feature_agent365_support
July 22, 2026 21:14
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0d367487-e88d-4423-8016-475637d47ed0
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0d367487-e88d-4423-8016-475637d47ed0
heyitsaamir
force-pushed
the
heyitsaamir-python-otel-apps
branch
from
July 22, 2026 21:16
18a5d99 to
2dae576
Compare
corinagum
approved these changes
Jul 22, 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
2 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.
Adds the Apps-side OpenTelemetry layer: inbound activity processing and handler telemetry.
Why
This gives developers the other half of the story: Teams called the app, the SDK processed the activity, and the right handler ran. When paired with the API layer below it, the trace reads like: inbound activity → handler → outbound Teams API → auth. Much less spelunking in logs, thank goodness.
This PR intentionally leaves Agent365-specific integration out of the SDK telemetry pass because that will land separately.
Interesting bits
microsoft.teams.activity.processaround inbound activity processing.microsoft.teams.handleraround handler dispatch.Microsoft.Teams.Appsas the instrumentation scope, with the package version attached as the scope version.Reviewer tips
Start with the app processing path, then check handler telemetry and the compatibility follow-up. This PR stacks on the API layer, so API outbound spans live in the parent PR.
Testing
Targeted Apps diagnostics/process tests pass after removing baggage. CI will rerun for this layer. The full stack was also live-smoked against Agent365/ACF and Echo/PokemonCatcher before splitting, with Aspire showing the expected Apps/API span nesting.