INFO logs printed to the stderr

[baruchiro]

The INFO level logs are printed to the stderr right now.

It is not right, because there is a common practice of running a CLI thought code, and following the stderr for errors.

Where should we print the INFO logs?

If we take the Docker execution, the easiest way to get the results from a Docker is by printing the Docker log into a file. With this practice, we will get the log inside our results file, which is not good.
On the other hand, the stdout of Docker is used for logs, and we need to track the logs.

So we can print to the stdout and force the Docker user to mount a volume and read the results file, or we can add a --quite flag to not log to the stdout.

[jossef]

error -> stderr
info -> stdout
debug -> stdout

• add --quiet flag to not print any logs to the stdout at all (if someone parses the output straight from stdout)

[baruchiro]

Example:
rs/zerolog#150 (comment)