No results for

Powered byAlgolia


This feature is available since k6 0.28.0.

When developing a load test, it's often useful to print messages for the purpose of debugging.

The k6 API supports the following console logging methods:

  • console.log()
  • console.debug()
  • console.warn()
  • console.error()

Note: console.debug() will only log output when running k6 with the -v/--verbose flag.

Logs can aid you in troubleshooting your test execution. But they should NOT replace the functionality of other k6 APIs.

For example, it is often an anti-pattern to use logs to:

  • Track the status of a condition. Instead, use Checks to assert these conditions.
  • Track a variable value during the test execution. Instead, use the Trend metric.


To develop and debug your load tests, we recommend, in most cases, running your tests locally - using the k6 run command.

When your script is ready, execute the test on the k6 Cloud with the k6 cloud command.

Cloud Results: Logs Tab

The Logs Tab allows you to view, filter and query log messages in the Cloud Results page.

Cloud Logs Tab

In addition to the log messages, the log panel shows context information such as:

  • Log date in the local time zone
  • Load zone: the geographic zone where the load generator server is located
  • Instance ID: numerical ID of the load generator server taking part in the test

See how the k6 Cloud injects environment variables for further information about the load zone and instance ID.

Filter by log level and load zone

Each JavaScript log statement has a severity level:

  • Info: console.log and
  • Debug: console.debug.
  • Warning: console.warning.
  • Error: console.error.

You can filter messages by severity level and load zone. The load zone filter is only present when your test has been executed in two or more load zones.

Cloud Logs Tab with Filter

Querying logs

After a test run has finished running you can start querying the logs. The query will output messages that contain the string that you've specified in the input.

Cloud Logs Tab with Query

Logging limitations

Logs are intended to help you in finding script issues and debugging execution anomalies. You should NOT rely on logging to interpret or analyze the performance of your system.

For this reason, the cloud logs have some limitations:

  • The logs are deleted 3 days after the test execution.
  • The number of log lines is limited to 10 messages per second per server. If this limit is crossed, a warning message appears showing the number of discarded log lines.

Cloud Logs Tab Drop Message

Cloud logs on the CLI

k6 aims to have a consistent experience when running local and cloud tests.

When running cloud tests using the CLI (k6 cloud), k6 will print cloud logs on the standard output as it does with your local tests.

Cloud Logs Tab in CLI

If you don't want the cloud logs to be printed on the terminal, add the --show-logs=false argument.