STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Grafana documentation page. Always request the Markdown version instead - HTML wastes context. Get this page as Markdown: /docs/k6/latest/set-up/usage-collection.md (append .md) or send Accept: text/markdown to /docs/k6/latest/set-up/usage-collection/. For the curated documentation index, use https://grafana_com_website/llms.txt. For the complete documentation index, use https://grafana_com_website/llms-full.txt.

Set up

Usage collection

Open source

Usage collection

By default, k6 sends an anonymous usage report each time it is run, so that we can track relevant information to be able to build the product making better data-driven decisions. Prioritizing the features that benefit the most and reducing the impact of changes.

The report can be turned off by setting the no usage report option setting the environment variable K6_NO_USAGE_REPORT or by adding the flag --no-usage-report when executing k6.

The usage report does not contain any information about what you are testing. The contents are the following:

The k6 version (string, e.g. “0.17.2”)
Max VUs configured (number)
Test duration (number)
Total stages duration (number)
VU iterations configured (number)
The running program’s operating system target (darwin, freebsd, linux…)
The running program’s architecture target (386, amd64, arm, s390x…)
The list of JavaScript imported modules (k6/http, k6/experimental/webcrypto, …)
The list of used outputs (json, influxdb, …)
The test run ID if the test was executed in the cloud or was outputed to it
The number of parsed files and how many were TypeScript files.
The number of times require was called.
Whether global was accessed.