-
Notifications
You must be signed in to change notification settings - Fork 331
Emit pool metrics and traces, and fix Count semantics in ChannelDbConnectionPool #4504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Open
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
018196a
Emit pool metrics and fix Count semantics in ChannelDbConnectionPool
mdaigle 6d7710d
Add pool tracing parity for ChannelDbConnectionPool
mdaigle 6f0261c
Give connection pools an injectable metrics sink
mdaigle 787823b
Define the pool metrics seam as an interface
mdaigle 2a0ed09
Remove trace-message parity tests
mdaigle efd55a0
Fix trace-message class/method references in pool V2
mdaigle c63d491
Adopt new trace message format in pool V2
mdaigle 56731d2
Simplify pool V2 trace call sites
mdaigle 2e0dcf9
Add missing coverage traces for warmup and connection retrieval
mdaigle a005f3c
Feed connection metrics through DbConnectionInternal's constructor
mdaigle 21644e4
Avoid duplicating base constructor defaults; drop dead pool helper
mdaigle a970bdd
Clean up test file structure.
mdaigle 14dbff1
Balance soft and hard disconnects when replacing a connection
mdaigle 563543e
Balance the pooled-connection gauge when replacing a connection
mdaigle 389d934
Address review feedback on metrics routing, sizing, and shared traces
mdaigle d36665e
Balance connection counters when activation fails
mdaigle 37307b8
Add coverage for the counters emitted when idle connections are pruned
mdaigle b8ec7a3
Keep the new trace format in PoolPruner
mdaigle c9dfe1c
Add unit coverage for the stasis connection counter
mdaigle 53dd42c
Merge branch 'main' of https://github.com/dotnet/SqlClient into dev/a…
mdaigle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only
ActivateConnectionandDeactivateConnectionwere moved onto this.SetInStasis,TerminateStasis, the non-pooledHardDisconnectRequestand bothEnter/ExitNonPooledConnectioncalls still go toSqlClientDiagnostics.Metrics, so one object reports to two sinks depending on which counter fires.The test consequence is the part I care about:
AssertCountersclaims any counter it doesn't name must be zero, butstasisConnectionsandnonPooledConnectionscan never be non-zero on the fake. Those rows pass vacuously and give us false confidence, and stasis is the counter sitting right next to the #3640 double-deactivation we're regression testing here.Can we route the rest through the instance too? If there's a reason not to, the vacuous rows should come out of
AssertCounterswith a note saying why.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Routed the remaining sites through the instance sink.
Worth noting this is a no-op in production. The factory hands every connection the process-wide instance, so
Metricsalready isSqlClientDiagnostics.Metricsthere. The value is that a test can now observe those counters.