Document EXTOBS obsolete diagnostics for extensions #49870
Conversation
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
Co-authored-by: gewarren <[email protected]>
Copilot
AI
changed the title
[WIP] Document obsolete diagnostics for extensions
Document EXTOBS obsolete diagnostics for extensions
Nov 12, 2025
Copilot finished work on behalf of
gewarren
November 12, 2025 20:52
gewarren
approved these changes
Nov 12, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds documentation for the EXTOBS0001 obsolete diagnostic from the dotnet/extensions repository, following the established SYSLIB diagnostic documentation pattern.
Key Changes:
- Adds documentation for
IResourceMonitorobsolescence (EXTOBS0001) with migration guidance to metrics-based resource monitoring - Updates the obsoletions overview to include a new EXTOBS section alongside existing SYSLIB diagnostics
- Adds EXTOBS0001 to the table of contents under a new "EXTOBS diagnostics" section
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| docs/fundamentals/syslib-diagnostics/extobs0001.md | New documentation page for EXTOBS0001 warning covering IResourceMonitor obsolescence, migration examples, and suppression guidance |
| docs/fundamentals/syslib-diagnostics/obsoletions-overview.md | Adds EXTOBS section to overview, updates text to reference both SYSLIB and EXTOBS diagnostic families, and refreshes "See also" links to focus on recent .NET versions |
| docs/navigate/tools-diagnostics/toc.yml | Adds EXTOBS diagnostics section to TOC with entry for EXTOBS0001 |
| .WithMetrics(builder => | ||
| { | ||
| builder.AddMeter("Microsoft.Extensions.Diagnostics.ResourceMonitoring"); | ||
| builder.AddConsoleExporter(); // Or use any other exporter. |
There was a problem hiding this comment.
The comment on line 58 states "Or use any other exporter" but according to the custom coding guidelines (CodingGuidelineID: 1000002), comments should end with a period if they contain more than three words. Change to "Or use any other exporter."
Updated the formatting and structure of the obsoletions overview documentation.
gewarren
reviewed
Nov 12, 2025
meaghanlewis
approved these changes
Nov 13, 2025
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.
Summary
Adds documentation for the two
EXTOBS0XXXobsolete diagnostic IDs from the dotnet/extensions repository, following the established pattern forSYSLIB0XXXdiagnostics.Fixes #49508
Changes
IResourceMonitorobsolescence with migration to metrics-based resource monitoring using OpenTelemetry observable instrumentsAddServiceLogEnricherobsolescence with migration to correctly-namedAddApplicationLogEnrichermethodsEach diagnostic page includes affected APIs, migration examples, and suppression guidance consistent with SYSLIB documentation patterns.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews