-
Notifications
You must be signed in to change notification settings - Fork 322
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: deploy response time collector #1521
feat: deploy response time collector #1521
Conversation
27f7c90
to
e1c674d
Compare
Codecov Report
@@ Coverage Diff @@
## main #1521 +/- ##
============================================
+ Coverage 66.44% 66.88% +0.43%
Complexity 323 323
============================================
Files 589 596 +7
Lines 111498 112299 +801
Branches 994 994
============================================
+ Hits 74084 75106 +1022
+ Misses 37207 36986 -221
Partials 207 207
Continue to review full report at Codecov.
|
but it is error prone 1. not safe between clusters, updating query_response_time might need a distributed lock 2. not thread safe neither, since it still allow getting the stats and mutate stats parally 3. lack of tests
use cmake based `find_package` to find cmake, which give more control and returned variables
bb4803d
to
ec88d4f
Compare
add sanity check when trying to delete records from DEPLOY_RESPONSE_TIME in name_server
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.
LGTM
close #1234
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?