You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could include the additional features for making more fine-grained logformat configuration considering that at the moment logformat can be only defined at the global layer.
a per-output logformat option for a fine-grained definition of the format for the specific output
The cloud supports the log-output option and it shouldn't be confused as did during an internal discussion with show logs option.
k6 has its own debug log messages that are not driven from the script console.log(), just run k6 run --verbose or k6 cloud --verbose with a script without any console.log() calls and you'll see them.
This and #1939 should be much easier to do after #2412 (and its connected PRs). It wasn't all that difficult before, to be fair, but now we should actually be able to test it easily and reliably.
Also, somewhat connected to #2414 (comment), we should slightly refactor how k6 waits for logs to be done... Though a WaitGroup will probably be better than a channel for multiple logs...
Feature Description
It could be useful to declare multiple log outputs at the same time for
k6 run
andcloud
commands.or a more advanced example
Logformat
It could include the additional features for making more fine-grained
logformat
configuration considering that at the moment logformat can be only defined at the global layer.logformat
option for a fine-grained definition of the format for the specific outputAn example with the previous advanced example:
Cloud
The cloud supports the
log-output
option and it shouldn't be confused as did during an internal discussion with show logs option.so the following example is still a valid case:
k6 cloud --verbose --log-output "file=debug.log" --show-logs=false script.js
Already existing or connected issues / PRs (optional)
--log-output
#2249--show-logs
option ink6 cloud
#2288The text was updated successfully, but these errors were encountered: