You can also make k6 output detailed statistics in JSON format by using the --out/-o option for k6 run, like this:
Or if you want to get the result gzipped, like this:
The JSON file will contain lines like these:
Each line will either contain information about a metric, or log a data point (sample) for a metric. Lines consist of three items:
- type - can have the values Metric or Point where Metric means the line is declaring a metric, and Point is an actual data point (sample) for a metric.
- data - is a dictionary that contains lots of stuff, varying depending on the "type" above.
- metric - the name of the metric.
This line contains information about the nature of a metric. Here, "data" will contain the following:
- "type" - the metric type ("gauge", "rate", "counter" or "trend")
- "contains" - information on the type of data collected (can e.g. be "time" for timing metrics)
- "tainted" - has this metric caused a threshold to fail?
- "threshold" - are there any thresholds attached to this metric?
- "submetrics" - any derived metrics created as a result of adding a threshold using tags.
This line contains actual data samples. Here, "data" will contain these fields:
- "time" - timestamp when the sample was collected
- "value" - the actual data sample; time values are in milliseconds
- "tags" - dictionary with tagname-tagvalue pairs that can be used when filtering results data
You can quickly create filters to return a particular metric of the JSON file:
And calculate an aggregated value of any metric:
For more advanced cases, check out the jq Manual
If you don't care about each individual metric measurement and instead want to see only the aggregated data, exporting the end-of-test summary data to a JSON file might be a better choice than using the JSON output described here. For more details, see --export-summary and handleSummary() in the end-of-test summary docs.