Change the verbosity of the logs or add new levels

Hello @bdepaula

This is an issue for discussing verbosity.

[LUMI] has configuration issues.
 Check that the connection is passwd-less.(ssh xxx@lumi-cluster)
 Check the parameters that build the root_path are correct:{scratch_dir/project/user} = {/zzz/yyy/xxx}
[LUMI-LOGIN] has configuration issues.
 Check that the connection is passwd-less.(ssh xxxx@lumi-cluster)
 Check the parameters that build the root_path are correct:{scratch_dir/project/user} = {/zzz/yyy/xxx}
[CRITICAL] 2024-09-27 17:46:16,025 Issues while checking the connectivity of platforms. [eCode=7014]
2024-09-27 17:46:16,025 More info at https://autosubmit.readthedocs.io/en/master/troubleshooting/error-codes.html

I think that these logs should be always displayed

Right now, we have by default:

[CRITICAL] 2024-09-27 17:46:16,025 Issues while checking the connectivity of platforms. [eCode=7014]
2024-09-27 17:46:16,025 More info at https://autosubmit.readthedocs.io/en/master/troubleshooting/error-codes.html

Also, some years ago, the users were complaining about the verbosity of the logs by default, so we added different autosubmit level logs that are not standard (one of the reasons for having the log folder that overloads the standard log lib ).

I think that the usage of Autosubmit is a little bit different from that time.

• Expert users are moving to use the GUI + nohup
• While the newbie users are using the console version of autosubmit run (without nohup). So, the log output may not fit their necessity as they would need something more verbose, like the debug level but perhaps not that detailed as a first experience. What do you think @bdepaula ?

Also, now autosubmit is more international so the info level is not enough for them and also they may not know that there are different levels of logs.

Edit: Another alternative is to revise the info/result level and add more stuff there