Skip to content

Improve clarity around logs behaviour in k6 #877

@yorugac

Description

@yorugac
Contributor

k6 has a bit unusual approach to the logs it prints in CLI output by default. Logs of all levels are written to stderr, unless --log-output option is used. With that option, logs of all levels are re-directed to the specified location. There is no difference in the logs behaviour by levels (INFO vs ERROR vs WARNING).

From the user's perspective, it appears as if this approach was taken to distinguish between test run process messages and summary in stdout and logs in stderr. This is a bit unusual from the perspective of CLI tooling, and it'd be useful for some use cases to be explicit about these details in the docs.

Activity

MattDodsonEnglish

MattDodsonEnglish commented on Nov 9, 2022

@MattDodsonEnglish
Contributor

👍 It'd be good to get more logs about docs. Now the only info is in the reference for a few scattered options.

Now that we have a new sidebar section called "Results output", I think it'd be pretty sensible to put a new page or collection of pages called Logs there.

ppcano

ppcano commented on Apr 4, 2023

@ppcano
Collaborator

Relates to #327

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Area: OSS ContentImprovements or additions to community/oss documentationType: needsMaintainerHelpGood issue for k6 maintainers

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @ppcano@yorugac@immavalls@MattDodsonEnglish

      Issue actions

        Improve clarity around logs behaviour in k6 · Issue #877 · grafana/k6-docs