K6: vus, vus_max and runs metrics not emitted

[caalle]

In latest version in develop vus, vus_max and runs are missing from the JSON output.

[liclac]

Internal metrics reporting accidentally slipped out of the engine in the refactor, adding it back ASAP.

[liclac]

Added metrics:

• vus
• vus_max
• iterations (was runs)
• taints (was errors)

The new names are to be more consistent with terminology used elsewhere.

[caalle]

Tried this out and the metrics are available. Although I'm seeing some weird timestamps on them:

{"type":"Point","data":{"time":"0001-01-01T00:00:00Z","value":50,"tags":null},"metric":"vus"}
{"type":"Point","data":{"time":"0001-01-01T00:00:00Z","value":150,"tags":null},"metric":"vus_max"}
{"type":"Point","data":{"time":"0001-01-01T00:00:00Z","value":0,"tags":null},"metric":"iterations"}
{"type":"Point","data":{"time":"0001-01-01T00:00:00Z","value":0,"tags":null},"metric":"taints"}
{"type":"Point","data":{"time":"2017-01-17T09:18:01.660657284+01:00","value":716.515819,"tags":{}},"metric":"login_wait_trend"}

The login_wait_trend is my own and its' timestamp looks correct, but vus, vus_max, iterations and taints looks like they start on year one.

Any thoughts on this @uppfinnarn ?

Edit: Going through the output, the values of the Points seems correct.

[ragnarlonn]

It is dates according to the newly established k6 calendar, where Gregorian year 2017 equals year 1?