-
Notifications
You must be signed in to change notification settings - Fork 70
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 a new command to test rate metrics #267
Conversation
For end to end testing, we use the `list_with_metrics` command. It only does one iteration though, which means we don't have output for counters and rates. This adds a new command running 2 iterations.
07d110a
to
e81284b
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.
Makes me wonder if we shouldn't really keep a single command (ie. ACTION_LIST_WITH_METRICS
) and just make sure that command returns all metrics, including rates. Do you see value in having two separate commands?
@@ -49,11 +51,14 @@ public void doSendServiceCheck(String checkName, String status, String message, | |||
System.out.println("=== JSON ==="); | |||
ObjectMapper mapper = new ObjectMapper(); | |||
mapper.enable(SerializationFeature.INDENT_OUTPUT); | |||
StringWriter writer = new StringWriter(); |
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.
👍
Ideally we'd have a command with a parameter flag. If we change the current we'll break our end to end tests. It may not be a huge deal, but in regular tests we like having the distinction between rate and non-rate. |
For end to end testing, we use the
list_with_metrics
command. It onlydoes one iteration though, which means we don't have output for counters
and rates. This adds a new command running 2 iterations.