arrival-rate executors do not report active VUs accurately, they report initialized VUs instead

[Dieviete]

In the console output of K6 you can easily see how many VUs are currently active. See picture k6 console output

In the .json output there is a metric "vus" and a metric "vus_max". I would expect "vus" to reflect the number of currently active virtual users. However, in my .json output, except for the entries where "vus" is 0, "vus" and "vus_max" always have the same value. See picture k6 .json output

Is this a bug? If not, how to generate the correct number of active VUs in the .json output?

[na--]

Thanks for reporting this! We've known about for a while, but we lost sight of it... 😞 It is something halfway between a bug and a missing feature, one of the compromises for the sake of expedience to finally get #1007 out of the door last year... 😅 Its time to get fixed might have finally come, however, so I'll edit this issue a bit and keep it open. We probably should take care of it together with the rest of the items in #1386 and #1944

To give some details about the issue: currently, arrival-rate executors can easily show in the progress bars precisely how many active VUs they are using. However, since multiple scenarios can be executed simultaneously, and the vus metric is reported by k6 every second and encompasses all scenarios (though that might also change, see #1833), arrival-rate executors report as active all initialized VUs, even when that might not be the case.

[Dieviete]

Thank you for the quick response ☺️

[jsolv]

Hello!
How about status of this issue?
I can't get current actual VU's in metrics (from influxDB) in Grafana like values progress bar show, only values after slash. But i think it's good to write value before slash also.

[na--]

Sorry @jsolv, nobody has worked on this yet. I added it to the next milestone, but I can't make any promises when we'll get to it... 😞 If someone wants to make a PR before we can, we can review it though!