Question
Log Level Settings from Designer studio is not reflecting for an activity where we have a logginglevel as "InfoForced"
Need help on stopping logs from an activity which is having a logging level as "InfoForced" without code changes. below are the details:
1) We have an activity where we are logging an entry in Pega logs and logging level was set to "InfoForced".
2) Now we want to stop this logging. We can do this by updating the activity. But this requires code changes and push the code live. Here we are looking an option to see, whether we can stop these logs by doing any configuration changes in Pega without code changes. Below are the option what we tried:
a) We tried to set the logging level to OFF from the legging level setting option from designer studio for the activity which is doing logging(DesignerStudio->System->Operations->Logs). This didn’t help us as we are still able to see the logs from that activity.
b) We tried to update the log4j.properteis file to add an entry to set the log Level as OFF(We added an specific entry for an activity). After we update this file we restarted the JVM and no luck. Still we are able to see the logs form that activity.
Any help is appreciated.
***Updated by moderator: Lochan to add Categories***
Hi Ujjwal,
Thanks for the response. We are able to control the logger level setting if the logger level is "Error/Debug/Warn/Info" set in an activity from designer studio. but as we set the logger level as "InfoForced" we are not able to change from designer studio/SMA/prlogging.xml file. is there any specific reason behind this?
I don't know how annoying the infoForced message is, and if you're trying to turn it off for performance or other reasons. One thing you might try is to create a separate logger in the prlogging file for the activity class, and make that a rolling log of let's say 1 Meg so that it doesn't get too big. Then it won't clutter up the PegaRULES log file, and also won't fill up the disk.