I'm against the capricious classification of logging in general. Who are we to
say whether a log message is a success or failure, or whether a log is really
an error? Maybe the error wants to be a debug?
I'd rather go with the more type generic whatever-you-want-to-be.log or just
whatever.log for short
--
Jason
On Mon, Apr 1, 2019, at 3:19 AM, Robert Munteanu wrote:
> Hi,
>
> I think for some time we have overlooked the operational aspects of
> Apache Sling and that it's high time to address this huge gap we have
> between developing with Sling and operating with Sling.
>
> One of the things that bothers me the most is that everything is
> written in the _error_ log file. That is absolutely setting us up for
> failure! Everytime I need to see what Sling is doing I have to go to
> the _error_ log, and this already brings about the idea of _errors_ in
> Sling.
>
> As we all know, there are no errors in Sling, there is only great
> success. I would therefore like to submit this simple patch to change
> the default log file name to success.log .
>
> Given the obviousness of the benefit, this discussion is open only for
> today.
>
> Thanks,
>
> Robert
>
> diff --git a/src/main/provisioning/sling.txt
> b/src/main/provisioning/sling.txt
> index 55f2d9b..5a4984c 100644
> --- a/src/main/provisioning/sling.txt
> +++ b/src/main/provisioning/sling.txt
> @@ -134,7 +134,7 @@
>
> org.apache.sling.commons.log.LogManager
> org.apache.sling.commons.log.pattern="%d{dd.MM.yyyy HH:mm:ss.SSS}\
> *%level*\ [%thread]\ %logger\ %msg%n"
> - org.apache.sling.commons.log.file="logs/error.log"
> + org.apache.sling.commons.log.file="logs/success.log"
> org.apache.sling.commons.log.level="info"
> org.apache.sling.commons.log.file.size="'.'yyyy-MM-dd"
> org.apache.sling.commons.log.file.number=I"7"
>
>
