Re: timestamp and thread name in StatusLogger

2022-08-28 Thread Ralph Goers
You seem to be forgetting that StatusLogger doesn’t use Log4j Core. It doesn’t write to rotated logs and cannot write to anything over the network. It only supports specifying a simple file name. At work, all my services use Spring Boot. They are configures with a default log4j2.yml that logs t

Re: timestamp and thread name in StatusLogger

2022-08-28 Thread Volkan Yazıcı
Thanks for the clarification Ralph. I understand the rationale for unix logs. I believe we should reassess this default for the following reasons: - Users rarely feed service app logs to system logs. Those who do, simply ingest lines intact without any timestamp prefixing. - I have never

Re: timestamp and thread name in StatusLogger

2022-08-26 Thread Ralph Goers
It does need to be optional. If you are running your app as a service on Linux/Unix the logs will already contain a timestamp because they get routed to the system log. So having a timestamp in them makes them ugly for that case. Ralph > On Aug 26, 2022, at 5:39 AM, Gary Gregory wrote: > > I'

Re: timestamp and thread name in StatusLogger

2022-08-26 Thread Ralph Goers
StatusLogger either uses SimpleLogger or StatusConsoleListener to print the log messages. If StatusConsoleListener is registered then it does print the date and thread name. When no listeners are registered SimpleLogger is used. If System Property log4j2.StatusLogger.DateFormat is defined the

Re: timestamp and thread name in StatusLogger

2022-08-26 Thread Gary Gregory
I've found that odd myself just like Maven output does not contain timestamps, might be for "simplest possible output". I'm all for adding these. Gary On Fri, Aug 26, 2022, 03:36 Volkan Yazıcı wrote: > Is there any particular reason we don't render the timestamp and thread > name in StatusLogge