-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add correlation ID for DbContext
like we have for DbCommand
and DbConnection
#16201
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
ajcvickers
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Jun 26, 2019
ajcvickers
added a commit
that referenced
this issue
Jun 29, 2019
…and `DbConnection` Based on feedback, now three IDs and a count: * Instance ID - set for the context instance and never changed * Pool ID - set for the pool instance and never changed * ID - * Pooling: set when leased; reset when returned. * No pooling: same as Instance ID * Leases * Pooling: A count of the number of times the context instance has been leased * Not pooling: zero Fixes #16201
ajcvickers
added a commit
that referenced
this issue
Jun 29, 2019
…and `DbConnection` Based on feedback, now three IDs and a count: * Instance ID - set for the context instance and never changed * Pool ID - set for the pool instance and never changed * ID - * Pooling: set when leased; reset when returned. * No pooling: same as Instance ID * Leases * Pooling: A count of the number of times the context instance has been leased * Not pooling: zero Fixes #16201
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
To make it easier to correlate events to the context instance being used.
The text was updated successfully, but these errors were encountered: