-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Reject non-numeric values for the Rate metric #908
Comments
I'm not sure we should ignore invalid values, we probably have to throw an error in such situations, to minimize any user confusion. |
I don't have strong opinion in either direction, as far as I can see there are 2 options:
There are annoying drawbacks with each option.
Option 2 would make it easy for the user to record correct data even when the SUT is overloaded and returning HTTP 400-500. In my case, server was returning HTTP-200, with correct headers until it got overloaded, and started returning 400 (without expected header). For option 1. the correct script code would have to be something like this: let res = http.get("http://test.loadimpact.com");
if(typeof res.headers.sql_count !== "undefined" ){
let req_sql_count = parseInt(res.headers.sql_count, 10);
sqlCount.add(req_sql_count);
} When writing scripts like this, it's tricky at first to predict that the |
Closing this in favor of the more comprehensive #1435. |
Example script that demonstrates the problem:
My expectation was for the
sqlCount
metric to ignore non-numeric values. Instead it accepts anything, but LoadImpact drops the entire data packages, so even data for the initial request is missing in the cloud.The text was updated successfully, but these errors were encountered: