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.
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
chore: support OpenTelemetry metrics #1465
chore: support OpenTelemetry metrics #1465
Changes from 2 commits
7c32521
6b1fbf9
7fa50c8
7e5536d
58e7193
fc9419c
14a82f0
68b244d
1e04b21
0c8347d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
databaseId
should never be null (at least not for a real connection, maybe in some tests it is). Could we therefore change this into a more direct implementation, where:metricAttributes
are always created whenExtendedQueryProtocolHandler
is created.metricAttributes
of thisExtendedQueryProtocolHandler
. It should also not takeDatabaseId
(or anything else) as an input argument, as theDatabaseId
is fixed for anExtendedQueryProtocolHandler
. The structure here is that:ConnectionHandler
.ConnectionHandler
andExtendedQueryProtocolHandler
.ExtendedQueryProtocolHandler
andBackendConnection
.DatabaseId
that never changes during their lifetime.Now it seems like
metricAttributes
sometimes needs to be created on-the-fly, but I don't think that is ever true.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.
Yes, I was originally creating
metricAttributes
inExtendedQueryProtocolHandler
and pass it to theBackendConnection
. But I thought we already passdatabaseId
into it in here. I need to construct the attributes inExecute
ofBackendConnection
.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.
I also think
databaseId
should not be null but I add this check due to an error. If I addmetricAttributes
as an instance method, can theExecute
ofBackendConnection
access it? Let me explore it more.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.
Please take a look my latest changes. Basically, I need the attributes in
Execute
ofBackendConnection
.