[RTC] Rename error.log to success.log

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

[RTC] Rename error.log to success.log

Robert Munteanu-2
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"

Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Roy Teeuwen
Hey Robert,

Why not call it sling.log? or status.log? Because it will still log errors / exceptions in the success.log this way

Greets,
Roy

> On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]> 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"
>

Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Eric Norman
In reply to this post by Robert Munteanu-2
Neither of those names are accurate though.  The file is just logs, there
isn't any reason to conclude that the contents are errors or successes.
The reality is a mix of log messages for lots of different reasons.

-Eric

On Mon, Apr 1, 2019, 12:19 AM Robert Munteanu <[hidden email]> 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"
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Nicolas Peltier-2
In reply to this post by Robert Munteanu-2
+1 i like that spirit.

Le lun. 1 avr. 2019 à 12:49, Robert Munteanu <[hidden email]> a écrit :

> 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"
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Julian Sedding-3
+1 One particular benefit of renaming would be the reduced number of
bug reports. That will give us more time to drink coffee.

Regards
Julian

On Mon, Apr 1, 2019 at 10:34 AM Nicolas Peltier
<[hidden email]> wrote:

>
> +1 i like that spirit.
>
> Le lun. 1 avr. 2019 à 12:49, Robert Munteanu <[hidden email]> a écrit :
>
> > 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"
> >
> >
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Carsten Ziegeler
It seems no one except me has heared of the latest trend in logging:
logless?

Instead of renaming lets go all the way!


Regards

Carsten


Julian Sedding wrote

> +1 One particular benefit of renaming would be the reduced number of
> bug reports. That will give us more time to drink coffee.
>
> Regards
> Julian
>
> On Mon, Apr 1, 2019 at 10:34 AM Nicolas Peltier
> <[hidden email]> wrote:
>>
>> +1 i like that spirit.
>>
>> Le lun. 1 avr. 2019 à 12:49, Robert Munteanu <[hidden email]> a écrit :
>>
>>> 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"
>>>
>>>
--
Carsten Ziegeler
Adobe Research Switzerland
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Konrad Windszus
In reply to this post by Roy Teeuwen
+1 to sling.log
-1 to success.log (because errors are still contained in there)

Konrad

> On 1. Apr 2019, at 10:18, Roy Teeuwen <[hidden email]> wrote:
>
> Hey Robert,
>
> Why not call it sling.log? or status.log? Because it will still log errors / exceptions in the success.log this way
>
> Greets,
> Roy
>
>> On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]> 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"
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Daniel Klco-2
I'm assuming the timing of this announcement is not accidental. Having just
returned from Adobe Summit and knowing they are one of the largest users of
Apache Sling, why not aligning with what I heard at the event:

revolutionary-customer-experience-platform-experiencing-digital-transformation-experiences-serverless.log


On a less facetious note, the idea of sling.log does have some merits as
the error.log also is logging status events, though I wonder how many log
analysis scripts will need to be updated by downstream consumers.

On Mon, Apr 1, 2019, 7:30 AM Konrad Windszus <[hidden email]> wrote:

> +1 to sling.log
> -1 to success.log (because errors are still contained in there)
>
> Konrad
>
> > On 1. Apr 2019, at 10:18, Roy Teeuwen <[hidden email]> wrote:
> >
> > Hey Robert,
> >
> > Why not call it sling.log? or status.log? Because it will still log
> errors / exceptions in the success.log this way
> >
> > Greets,
> > Roy
> >
> >> On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]> 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"
> >>
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Georg Henzler-2
In reply to this post by Konrad Windszus
Hi,

On 2019-04-01 13:30, Konrad Windszus wrote:
> +1 to sling.log
> -1 to success.log (because errors are still contained in there)

+1 for sling.log over success.log

> ...I wonder how many log analysis
> scripts will need to be updated by downstream consumers

I'm also a bit worried about that. I think the initial reason for
error.log to be named like this is that httpd also uses error.log - I'd
be fine to leave it error.log as well (given that the most common reason
to look at this file is probably still analysing errors...)

-Georg

>
> Konrad
>
>> On 1. Apr 2019, at 10:18, Roy Teeuwen <[hidden email]> wrote:
>>
>> Hey Robert,
>>
>> Why not call it sling.log? or status.log? Because it will still log
>> errors / exceptions in the success.log this way
>>
>> Greets,
>> Roy
>>
>>> On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]> 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"
>>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Jason E Bailey
In reply to this post by Robert Munteanu-2
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"
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Robert Munteanu-2
In reply to this post by Georg Henzler-2
On Mon, 2019-04-01 at 14:53 +0200, Georg Henzler wrote:
> > ...I wonder how many log analysis
> > scripts will need to be updated by downstream consumers
>
> I'm also a bit worried about that. I think the initial reason for
> error.log to be named like this is that httpd also uses error.log -
> I'd
> be fine to leave it error.log as well (given that the most common
> reason
> to look at this file is probably still analysing errors...)

You are probably right about the historical reasons for using
'error.log' . Additionally, the log format specification follows the
LogFormat and CustomLog directives from httpd

https://sling.apache.org/documentation/development/client-request-logging.html

Thanks,

Robert

Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Robert Munteanu-2
In reply to this post by Daniel Klco-2
On Mon, 2019-04-01 at 07:57 -0400, Daniel Klco wrote:
> I'm assuming the timing of this announcement is not accidental.
> Having just
> returned from Adobe Summit and knowing they are one of the largest
> users of
> Apache Sling, why not aligning with what I heard at the event:
>
> revolutionary-customer-experience-platform-experiencing-digital-
> transformation-experiences-serverless.log

No, the timing is not accidental :-)

>
>
> On a less facetious note, the idea of sling.log does have some merits
> as
> the error.log also is logging status events, though I wonder how many
> log
> analysis scripts will need to be updated by downstream consumers.

Yes, this has come up from Konrad as well. I will start a different
discussion for it, but tomorrow :-)

Thanks,

Robert

>
> On Mon, Apr 1, 2019, 7:30 AM Konrad Windszus <[hidden email]> wrote:
>
> > +1 to sling.log
> > -1 to success.log (because errors are still contained in there)
> >
> > Konrad
> >
> > > On 1. Apr 2019, at 10:18, Roy Teeuwen <[hidden email]> wrote:
> > >
> > > Hey Robert,
> > >
> > > Why not call it sling.log? or status.log? Because it will still
> > > log
> > errors / exceptions in the success.log this way
> > > Greets,
> > > Roy
> > >
> > > > On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]>
> > > > 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"
> > > >

Reply | Threaded
Open this post in threaded view
|

Re: [RTC] Rename error.log to success.log

Christian Schneider
In reply to this post by Konrad Windszus
I also like sling.log.

It is is neutral in respect to error or not and clearly communicates the
purpose.

Christian

Am Mo., 1. Apr. 2019 um 13:30 Uhr schrieb Konrad Windszus <[hidden email]>:

> +1 to sling.log
> -1 to success.log (because errors are still contained in there)
>
> Konrad
>
> > On 1. Apr 2019, at 10:18, Roy Teeuwen <[hidden email]> wrote:
> >
> > Hey Robert,
> >
> > Why not call it sling.log? or status.log? Because it will still log
> errors / exceptions in the success.log this way
> >
> > Greets,
> > Roy
> >
> >> On 1 Apr 2019, at 09:19, Robert Munteanu <[hidden email]> 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"
> >>
> >
>
>

--
--
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com
Reply | Threaded
Open this post in threaded view
|

[DISCLOURE] [RTC] Rename error.log to success.log

Robert Munteanu-2
In reply to this post by Robert Munteanu-2
Hi,

I should disclose the fact that I started this as an April Fool's joke.

Much to my surprise, a constructive discussion has come up about the
log name and I'll follow-up on a different thread about those
proposals.

Thanks!

Robert

P.S. Same time, next year :-)

On Mon, 2019-04-01 at 09:19 +0200, 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"
>