.NET: document host-owned telemetry and message content controls - #8492
Draft
Naveen Chatlapalli (1aifanatic) wants to merge 2 commits into
Draft
Naveen Chatlapalli (1aifanatic) wants to merge 2 commits into
Naveen Chatlapalli (1aifanatic) wants to merge 2 commits into
Conversation
Naveen Chatlapalli (1aifanatic)
deployed
to
github-app-auth
September 18, 2026 02:07 — with
GitHub Actions
Active
Naveen Chatlapalli (1aifanatic)
deployed
to
github-app-auth
September 18, 2026 02:08 — with
GitHub Actions
Active
Naveen Chatlapalli (1aifanatic)
deployed
to
github-app-auth
September 18, 2026 02:08 — with
GitHub Actions
Active
Copilot started reviewing on behalf of
Naveen Chatlapalli (1aifanatic)
September 18, 2026 02:08
View session
Naveen Chatlapalli (1aifanatic)
deployed
to
github-app-auth
September 18, 2026 02:08 — with
GitHub Actions
Active
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Identify the meter name required by AddMeter and distinguish it from the application’s custom meter.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Documents existing .NET OpenTelemetry configuration and sensitive message-content controls without changing APIs or defaults.
Changes:
- Documents
UseOpenTelemetryandEnableSensitiveData = false. - Explains host-owned provider, source, and meter subscriptions.
- Clarifies content suppression versus event emission and distro limitations.
File summaries
| File | Summary |
|---|---|
dotnet/samples/02-agents/AgentOpenTelemetry/README.md |
Adds telemetry configuration and sensitive-data guidance. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite (auto)
Note
Copilot is running an experiment and ran this review at Lite.
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Naveen Chatlapalli (1aifanatic)
deployed
to
github-app-auth
September 18, 2026 04:27 — with
GitHub Actions
Active
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.
Motivation & Context
The .NET portion of #8412 needs evidence about existing controls before introducing an API modeled on Python instrumentation. Applications also need to preserve telemetry providers and exporters owned by their host.
Description & Review Guide
Related Issue
Contributes to #8444; deliberately leaves it open pending maintainer confirmation of the distribution-specific requirement. No other open .NET PR for this issue was found. Python changes in #8451 are separate.
Contribution Checklist