Compact output metrics

[jgaalen]

Currently, K6 stores way too many values per single request to influxdb or whatever output you use causing a very high overhead in terms of network bandwidth, cpu and storage. Per request it stores 4 lines (data sent, received, duration and failed).

It would be incredibly more efficient to be able to store a single metric per requests, which holds all the data such as the data sent, received, status (failed true/false), duration and url, etc..

[inancgumus]

Hi @jgaalen, this issue sounds similar to #1321. Can you confirm?

[joanlopez]

It would be incredibly more efficient to be able to store a single metric per requests, which holds all the data such as the data sent, received, status (failed true/false), duration and url, etc..

Could you explain this more extensively, please? @jgaalen

What do you understand by "a single metric per requests, which holds all the data such as the data"?

I'd love to see some concrete examples about how that data would look like in plaintext.

Thanks! 🙇🏻