Logging in pyaerocom

[lewisblake]

Should we consider switching to a different logger (e.g., https://github.com/Delgan/loguru?tab=readme-ov-file#no-handler-no-formatter-no-filter-one-function-to-rule-them-all)

The logs are not currently being utilized effectively. They should be informative, easy(-ish) to read, and give detailed feedback when a crash occurs. There has been some significant work that's gone into making the logs customizable. A preferred solution would allow a drop in replacement which utilizes the customization allowed in logging.ini.

[heikoklein]

I use the logging extensively, in particularly when debugging others runs, when adressing memory usage etc. I know that our modellers use them as well, e.g. Anna and David.

We had a completely broken logging a year ago, with log-files so big that nobody could look at them. We have reworked them to a pretty useful state which allows logging.ini and logs in a proper size.

Logging can be very tricky, but it is currently not restricting us in any way. There is always a nicer, cooler, different logger out there, but if any, it is not the logging-software, but the log-statements which are difficult to choose.

Let's revisit logging every 5 years, i.e. in 4 years time again, so we don't spent too much time on such discussions.

[lewisblake]

Is it possible to configure the logger to show the entire stack trace to be displayed, including values of variables? While colors and cleanliness certainly aid in readability, getting the values in the entire stack trace is a feature I find especially compelling.