-
Notifications
You must be signed in to change notification settings - Fork 24.4k
show sub-commands INFO latencystats and LATENCY HISTOGRAM #10103
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
Conversation
oranagra
left a comment
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.
good catch!
|
we also need to modify |
OK, and |
sorry.. i didn't like the fact latency_histogram just took the second element without matching the name of the command (first list element). i didn't like the fact we repeadadly call the same command to validate different things on the same output. (this also messed up the count when trying to validate the count) adding validation of the sub-command name when calling the unfiltered LATENCYH HISTOGRAM
|
@filipecosta90 @soloestoy FYI see the test cleanup i did in 466bf66 (converting the response to a dict and doing explicit lookups) |
since
info commandstatsalready shows sub-commands, we should do the same ininfo latencystats.similarly, the LATENCY HISTOGRAM command now shows sub-commands (with their full name) when: