Fix incorrect .NET version numbers in built-in-metrics-diagnostics.md

[Copilot]

The documentation contained incorrect .NET version numbers that didn't follow the standard versioning format used throughout the docs. Several metrics were incorrectly labeled with versions like ".NET 8.8.0" and ".NET 9.8.0" instead of the proper ".NET 8.0" and ".NET 9.0" format.

This PR fixes 5 instances of incorrect version numbers:

• 3 instances of ".NET 8.8.0" corrected to ".NET 8.0"
• 2 instances of ".NET 9.8.0" corrected to ".NET 9.0"

The affected metrics were:

• container.cpu.limit.utilization
• container.cpu.request.utilization
• container.cpu.time
• container.memory.limit.utilization
• container.memory.usage

The corrected versions now align with the standard .NET version format used consistently throughout the documentation (e.g., ".NET 8.0", ".NET 9.0").

Fixes #45089.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

---

Internal previews

📄 File	🔗 Preview link
docs/core/diagnostics/built-in-metrics-diagnostics.md	.NET extensions metrics

[gewarren]

LGTM. @evgenyfedorov2 can you confirm that these were the versions you intended?

[evgenyfedorov2]

LGTM. @evgenyfedorov2 can you confirm that these were the versions you intended?

Hmm, actually, .NET Extensions is released monthly and the version numbers in documentation reflect the versions numbers when the code was released with .NET Extensions.

I don't know what the policy is, though? If a metric was released with .NET Extensions 9.8.0, can we say it is available with .NET 9.0?

[gewarren]

If a metric was released with .NET Extensions 9.8.0, can we say it is available with .NET 9.0?

Yes, I think so, if these metrics are released as part of the servicing releases. Perhaps we can say .NET 9 (servicing). If they are released via NuGet package, then I think we could just list the first package version they were available in.

[evgenyfedorov2]

If they are released via NuGet package, then I think we could just list the first package version they were available in.

Yes, they are part of the https://www.nuget.org/packages/Microsoft.Extensions.Diagnostics.ResourceMonitoring Nuget package. So instead of .NET 8.8.0, we can probably say Microsoft.Extensions.Diagnostics.ResourceMonitoring 8.8.0

[learn-build-service-prod]

PoliCheck Scan Report

The following reports lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a comment that you post to the PR. The feedback helps reduce false positive instances in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.