feat: add martin-tracing-utils for configuring tracing (1/3)

[CommanderStorm]

This is the first PR to break out of #1720 to make it reviewable.

The purpose is mainly to see if the added utilities are

• read & undaerstandable
• not magic for others and
• not too verbose
• and the name martin-tracing-utils okay.

Current usage of this code would be

// since logging is not yet available, we have to manually check the locations
let log_filter = LogLevel::from_argument("--log-level")
    .or_in_config_file("--config", "log_level")
    .or_env_var("MARTIN_LOG_FORMAT")
    .lossy_parse_to_filter_with_default("martin=info");
let log_format = LogFormat::from_argument("--log-level")
    .or_in_config_file("--config", "log_format")
    .or_env_var("RUST_LOG")
    .or_default(LogFormatOptions::Compact);
MartinObservability::from((log_filter, log_format))
    .with_initialised_log_tracing()
    .set_global_subscriber();

[CommanderStorm]

@nyurik @sharkAndshark might it be possible to get an review on this one? 👉🏻👈🏻

This would really help me push towards #1720 which (for me) currently kind of blocks the refactoring #1805 (comment)

[CommanderStorm]

We talked this out offliline and we will move this to different places:

• intialise a basic tracing
• take the configuration from the existing config
• update the running tracing config

I will reasses if this works and come back with a different PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​tracing-log@​0.2.0
	cargo/​tracing-subscriber@​0.3.20

View full report