Writing good log messages is a bit like writing good code. You may encouter
wild
variations in quality as well as style.
Anyway, my suggestion would be to go over the logs which each developer and
show
them better ways of coming up with informative log messages, on a case by case
basis. With
Hi
In my company, there are different developer working on the same
project and each has their own style of writting log messages.
Some use active, some use pasive, some print the exception message,
whereas some will print the entire stack trace, and the worst, some
simply print the
