How to handle logging in console clients

[josecelano]

Relates to: #917

In some console clients, we mixed the logging output (standard output) with the app response in JSON format (standard output).

Ideally, we should have a clean JSON that can be parsed easily or sent to the next app in the pipeline.

I see only one option.

Option 1: use a file for logging

We can redirect the logs to a file instead of using standard output. The file could have a default location or be overwritten.

If there is an error, we can write the error to the standard output in a JSON format if we want to show the error to the user and write the error to the log file if we only want to track it internally.

[josecelano]

Option 2: quite and debug flags

• quite: only json or errors also in JSON.
• debug: we can mix JSON output and logging info.

Example:

cargo run --bin udp_tracker_client announce --quite 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422