-
Notifications
You must be signed in to change notification settings - Fork 1.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
feat(storage): database/transaction/cursor metrics #5149
Conversation
shekhirin
commented
Oct 23, 2023
•
edited
Loading
edited
89040ca
to
b6c4162
Compare
b6c4162
to
dcf0e2b
Compare
6e4f643
to
43631ed
Compare
Codecov Report
... and 476 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
3619ccc
to
ea52657
Compare
1954eec
to
f0887f1
Compare
b87e9a9
to
63449f6
Compare
e81e422
to
e0aefc7
Compare
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.
hmm, what's the motivation for using a channel for metrics updates? I guess for more sophisticated reporting that requires more work than just increasing or decreasing metric values like histograms etc?
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.
this looks great!
would love to see some additional docs for the new metrics type, otherwise lgtm
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.
changes lgtm
not sure about the operation specific metrics