Mihail Stoykov

Hi @abadelt, I was recently told, by @bboreham, about the stastd_exporter [`ttl` configuration](https://github.com/prometheus/statsd_exporter/blob/f39c9c3645e78c7b4c505438130553205dce5af8/README.md#time-series-expiration) which will likely help you. You will need to come up with a number, but I would...

Thanks for reporting this @kkriegkxs, This seems to be [go stdlib thing](https://pkg.go.dev/net/http#Request.Write). As `""` is still something (it isn't `nil`) k6 makes a zero length body and sets Content-Length to...

> which is contrary to the claim above we do set it https://github.com/grafana/k6/blob/ece4633407ba2e88f82aa2781a183fd2a4278920/lib/netext/httpext/request.go#L166 it just isn't sent, probably because of the `chunked` encoding.

1. Hmm ... I would think the golang lib will do this by default :thinking: And it does ... it is just that k6 [deletes it](https://github.com/loadimpact/k6/blob/b3e4927d048a54f38204432bc90957daee7884e6/lib/netext/httpext/request.go#L307) :facepalm: Which was done...

Hi @badeball, I would recommend using [`k6/execution`](https://k6.io/docs/javascript-api/k6-execution/) instead of `__VU` as that will (more correctly) work in distributed/cloud run as well. For example using [`execution.vu.idInTest`](https://k6.io/docs/javascript-api/k6-execution/#vu). > Is( there a way...

The error you are getting in the tests is due to https://github.com/grafana/k6/pull/2602/commits/1b0e24e803cfd9281715c724b60db02f370c0433 . You should probably bump the k6 version in the extension and fix it there for now.

This is now supported since #2222, but is still not documented as can be seen in https://github.com/grafana/k6-docs/issues/664 to use it you need to set the `GODEBUG` env variable to `http2client=0`...

@liclac, This is what is used in all the multi NIC implementations, one of which will hopefully get in v0.28.0 ;). And it really does work and if you have...

I guess we should also mention that @simskij build https://github.com/k6io/operator which is a way to run k6 tests inside of kubernetes, again with the lack of thresholds and summary.

above [operator](https://github.com/k6io/operator) now also has a [blog post](https://k6.io/blog/running-distributed-tests-on-k8s/) explaining in more detail how to use it and what the tradeoffs are.