You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you make HTTP requests with redirects, the name tag in the generated metrics is wrong - it contains the original URL... For example, if you run the following script:
with k6 run --out json=results.json script.js, and then filter the generated metrics with to get the url tags with jq '. | select(.type=="Point" and .metric == "http_reqs") | .data.tags.url' results.json, you'd get this:
which is perfectly fine, but if you get the name tag with jq '. | select(.type=="Point" and .metric == "http_reqs") | .data.tags.name' results.json, you'd get:
If we had explicitly specified such a name tag, or anything other in the http.get()params, it would be fine. But in this case, the result of these 2 commands should have been identical...
Closes#1474
The root cause was reusing the same 'name' tag for all requests
processed by a transport. In the case of redirects and digest auth the
transport would process more than one request and needs to update the
'name' tag in the same way as 'url' is, but only for the initial
request, as subsequent ones will by dynamically generated.
Moved it back to v0.28.0, since the fix turned out to be more tricky than expected, and blurred the line between a bugfix and a minor breaking change... 😞
Closes#1474
The root cause was reusing the same 'name' tag for all requests
processed by a transport. In the case of redirects and digest auth the
transport would process more than one request and needs to update the
'name' tag in the same way as 'url' is, but only for the initial
request, as subsequent ones will by dynamically generated.
Closes#1474
The root cause was reusing the same 'name' tag for all requests
processed by a transport. In the case of redirects and digest auth the
transport would process more than one request and needs to update the
'name' tag in the same way as 'url' is, but only for the initial
request, as subsequent ones will by dynamically generated.
When you make HTTP requests with redirects, the
name
tag in the generated metrics is wrong - it contains the original URL... For example, if you run the following script:with
k6 run --out json=results.json script.js
, and then filter the generated metrics with to get theurl
tags withjq '. | select(.type=="Point" and .metric == "http_reqs") | .data.tags.url' results.json
, you'd get this:which is perfectly fine, but if you get the
name
tag withjq '. | select(.type=="Point" and .metric == "http_reqs") | .data.tags.name' results.json
, you'd get:If we had explicitly specified such a
name
tag, or anything other in thehttp.get()
params
, it would be fine. But in this case, the result of these 2 commands should have been identical...The consequence of this in the cloud is even worse, since the
name
tag is used for request grouping, it looks like this:The text was updated successfully, but these errors were encountered: