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 <[email protected]> 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 <[email protected]> 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 via email to