Mihail Stoykov

> > One improvement might be to pass actual functions to "exec" instead of a string > > Unfortunately, this probably wouldn't be possible. In the init context, k6 has...

cc @na-- for when you have time. #1499 Would probably need to take this into account. Although I guess we have postponed working on that since forever ... The PR...

- https://community.k6.io/t/how-to-distribute-vus-across-different-scenarios-with-k6/49/11 Is the thing not supported something like `exec.vu.idInScenario`? That seems possible at first glance at least. - https://github.com/grafana/k6-operator/issues/64 is strange from the issue definition it seems more like...

I don't think the "flexible" approach is actually what we want(or at least I see no real benefits to it): 1. What is the point of you being able to...

@emil45 as I mentioned in https://github.com/loadimpact/k6/issues/1730#issuecomment-796869067 I've managed to use telegraf + `namepass` fields to drop some metrics as a workaround. (I expect that predominantly we want to exclude metric...

Another workaround is to filter the logs using a pipe and grep(or jq for that matter) as in: ```bash mkfifo pipe cat < pipe | grep 'http_req_duration' >new.csv & //...

Potentially relevant documentation issue https://github.com/grafana/k6-docs/issues/616

As an additional note the HTTP2 RFC [specifies](https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2) that all header field names MUST be lower case. Which IMO makes fixing this even less relevant as the world moves more...

> Since the original issue is that k6 is internally changing the header to some camel-case format, won't you have to fix this to support HTTP2 since it "MUST be...

This will likely also mean that we need code to: 1. copy the old config in the place of the new one if it doesn't exist. But print warning if...