Hi 

Did you try from SMA?

If not, then try from SMA.

https://collaborate.pega.com/question/how-can-i-set-log-levels-sma-particular-class

Thanks

I was under the impression loggers would usually default to ALERT. So I don't think this setting would help in this instance.

Additionally, I've examined the underlying code and can only see logger outputs on WARN, INFO, ERROR.

For the actual problem, is it that you have started a listener and this appears to stop for unknown reasons?

If so, is there anything else in the logs, such as Exceptions which may indicate what the problem is?

If so, did you ex

Hi Bhanu,

In Pega 7.2.2, I think prlog4j2.xml is being used. Have you tried to add the logger in this file?

Regards

Simon

Hi

Please ignore my previous post.

Please refer the following links. This may help.

https://collaborate.pega.com/question/set-logging-level-permanently

https://community.pega.com/

Thanks

Hi 

for permanent logging, setting logging level in the prlogging.xml is the right approach in 7.2.2 version.

I suspect you used the CONSOLE appender-ref, which will not redirect to pegarule log. 

unless you have a requirement to use different logfile, i think the simplest way is to just define category, and desired logging level in the priority. this should sent to all the root loggers defined for ex,

<category name="com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl" additivity="false">
<priority value="debug"/>
</category>

However as Laurence mentioned, all loggers are defaulted to "Alert" level, so not sure if adding a logging level will help your requirement, as in case a Listener goes down, there should be an associated error, which will be logged in the logs anyways.