[6.1] Backport initial metrics enablement#3718
Merged
cheenamalhotra merged 1 commit intodotnet:release/6.1from Oct 28, 2025
Merged
[6.1] Backport initial metrics enablement#3718cheenamalhotra merged 1 commit intodotnet:release/6.1from
cheenamalhotra merged 1 commit intodotnet:release/6.1from
Conversation
cheenamalhotra
approved these changes
Oct 24, 2025
Member
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release/6.1 #3718 +/- ##
================================================
- Coverage 69.69% 59.32% -10.37%
================================================
Files 281 273 -8
Lines 62413 61434 -979
================================================
- Hits 43500 36448 -7052
- Misses 18913 24986 +6073
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
apoorvdeshmukh
approved these changes
Oct 27, 2025
This was referenced Nov 14, 2025
Merged
Merged
This was referenced Jan 16, 2026
Closed
This was referenced Jan 25, 2026
Open
This was referenced Feb 2, 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
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.
Description
This backports 66a67bc from #3575 to 6.1.
It's possible to start an application with the M.D.S EventSource already enabled, even before the static constructor for SqlClientEventSource has run. In this situation, the constructor for
Logwill runOnEventCommandwith an enablement command before it finishes executing. This enablement tries to callMetrics.EnableEventCounters, but this hasn't been initialized yet - it relies on theSqlClientEventSourceinstance.To break this cycle, we record the desired startup state of the metrics in this case, and pass it to the
SqlClientMetricsconstructor.Issues
Fixes #3711.
Testing
The timing makes this difficult to test. In the end, I built a test application locally, referenced 6.1.2 and ran
This allowed me to reproduce the problem: the counters appear in 6.0, don't appear in 6.1.2, appear again in 7.0-preview2 and now also appear in my local build.
Could someone run CI please? @empowerRob you should be able to verify with the nupkg build artifact.