Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Logger Threshold doesn't work

Avatar

Level 2

Hi,

I changed the error log threshold from "info" to "warn". Still I see info messages in my log. I want to get rid of these info messages and I want to log only warn and error logs in the error log file. 

I checked this link : http://cq-ops.tumblr.com/post/78113074496/how-to-suppress-informational-log-messages-from

But I dont want to create the log for any specific bundle or class. I want to have all warn/error logs at one place so the server maintenance team can identify the real problems more easily. Am I missing something in the configuration ?

Can someone help me how to achieve this ?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi,

From what I know you cannot have WARN/ERROR messages in one log and the INFO messages in another log. You might want to ask on the Sling mailinglist though if that's possible.

Jörg

View solution in original post

6 Replies

Avatar

Employee

Can you share some sample/more details on your config?

Avatar

Level 2

Hi Feike,

I am not using any custom Logger osgi:config. This is the OOTB available in Felix console Logger. I am attaching the screenshot for your reference.

Thanks,

Narendra N

Avatar

Employee

Can you check this url? /system/console/slinglog

Gives a better overview.

Avatar

Level 2

If I change the Root Sling Logger configuration, I see only ERROR and WARNs in error log, which is good. But here is the real problem. If I create a new logger configuration called logs/info.log and provide the class as org.apache.pdfbox with INFO threshold, it doesn't log anything. I want to have two separate log files for ERROR/WARN and INFO.

Avatar

Correct answer by
Employee Advisor

Hi,

From what I know you cannot have WARN/ERROR messages in one log and the INFO messages in another log. You might want to ask on the Sling mailinglist though if that's possible.

Jörg