Enable colour in console output

[josecelano]

Enable colour in console output.

We were using the logging crate for logging. We move to tracing but keeping the same format for logs. The only difference was the colour introduced by the tracing crate. This is just a patch to allow using color with tracing. We parse the logs to extract the running services for example from these lines:

2024-06-10T16:07:39.989540Z  INFO torrust_tracker::bootstrap::logging: logging initialized.
2024-06-10T16:07:39.990205Z  INFO UDP TRACKER: Starting on: udp://0.0.0.0:6868
2024-06-10T16:07:39.990215Z  INFO UDP TRACKER: Started on: udp://0.0.0.0:6868
2024-06-10T16:07:39.990244Z  INFO UDP TRACKER: Starting on: udp://0.0.0.0:6969
2024-06-10T16:07:39.990255Z  INFO UDP TRACKER: Started on: udp://0.0.0.0:6969
2024-06-10T16:07:39.990261Z  INFO torrust_tracker::bootstrap::jobs: TLS not enabled
2024-06-10T16:07:39.990303Z  INFO HTTP TRACKER: Starting on: http://0.0.0.0:7070
2024-06-10T16:07:39.990439Z  INFO HTTP TRACKER: Started on: http://0.0.0.0:7070
2024-06-10T16:07:39.990448Z  INFO torrust_tracker::bootstrap::jobs: TLS not enabled
2024-06-10T16:07:39.990563Z  INFO API: Starting on http://127.0.0.1:1212
2024-06-10T16:07:39.990565Z  INFO API: Started on http://127.0.0.1:1212
2024-06-10T16:07:39.990577Z  INFO HEALTH CHECK API: Starting on: http://127.0.0.1:1313
2024-06-10T16:07:39.990638Z  INFO HEALTH CHECK API: Started on: http://127.0.0.1:1313

We extract these running services:

{
  "udp_trackers": [
    "127.0.0.1:6969"
  ],
  "http_trackers": [
    "http://127.0.0.1:7070"
  ],
  "health_checks": [
    "http://127.0.0.1:1313/health_check"
  ]
}

We should refactor the output format to take advantage of the new tracing crate. tracing supports structured fields on spans and events, so it would be easier to parse those services.

[josecelano]

Sample coloured output:

[codecov]

Codecov Report

Attention: Patch coverage is 86.20690% with 4 lines in your changes missing coverage. Please review.

Project coverage is 78.53%. Comparing base (4832235) to head (eb928bc).

Files	Patch %	Lines
src/bootstrap/logging.rs	0.00%	1 Missing ⚠️
src/console/ci/e2e/runner.rs	0.00%	1 Missing ⚠️
src/console/clients/checker/app.rs	0.00%	1 Missing ⚠️
src/console/clients/udp/app.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #896      +/-   ##
===========================================
+ Coverage    78.50%   78.53%   +0.03%     
===========================================
  Files          171      171              
  Lines         9443     9458      +15     
===========================================
+ Hits          7413     7428      +15     
  Misses        2030     2030              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[josecelano]

Regarding using tracing capabilities, for example, the folowwing Rust logging line:

info!(target: "UDP TRACKER", "Started on: udp://{}", address);

Produces this output:

2024-06-14T16:20:54.690047Z  INFO UDP TRACKER: Started on: udp://0.0.0.0:6969

But we could use instead:

event!(target: "UDP TRACKER", Level::INFO, started_on_socket_address = format!("udp://{}", address.to_string()));

Which produces:

2024-06-14T16:20:54.690052Z  INFO UDP TRACKER: started_on_socket_address="udp://0.0.0.0:6969"

I guess the second one is easier to parse: started_on_socket_address="THE_URL".

And it scales much better, we can add more fields. We have to research how this fits with new login styles like JSON format.

cc @da2ce7

[josecelano]

ACK eb928bc