Question
Atos Syntel
IN
Last activity: 6 Jul 2017 6:17 EDT
How do log events of levels of INFO and WARN get logged when you have set the priority value to ALERT
Below is the setting from my prlogging.xml file, the priority level is not changed in any of the appenders.
<root>
<priority value="alert"/>
<appender-ref ref="ASYNC"/>
<appender-ref ref="ALERT-ASYNC"/>
</root>
when you select ALERT as the logging level, only log events above ALERT level should be logged, but i can see log events of level INFO and WARN in the PegaRules log file, how are these events getting logged.
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
Pegasystems Inc.
US
By default, logging level is NULL for any logger (core classes or rules) i.e the level is not set, so the logging level is taken from 'root' logger (which is ALERT as set in prlogging.xml). But yes as "Ama_deus" mentioned, this is overridden when you use oLog.warnForced() or oLog.infoForced().
For any activity class, you can use oLog.isInfoEnabled() to verify if INFO is enabled for the activity logger in question.
Pegasystems Inc.
US
That is the root level setting, correct? Do you have any settings inside "category" elements that are more verbose?
See this reference : https://docs-previous.pega.com/system-administration/84/customizing-logs
I would stick to the log4j levels :
- fatal
- error
- warn
- info
- debug
Accepted Solution
Pegasystems Inc.
US
By default, logging level is NULL for any logger (core classes or rules) i.e the level is not set, so the logging level is taken from 'root' logger (which is ALERT as set in prlogging.xml). But yes as "Ama_deus" mentioned, this is overridden when you use oLog.warnForced() or oLog.infoForced().
For any activity class, you can use oLog.isInfoEnabled() to verify if INFO is enabled for the activity logger in question.