INFO logging does not work despite correct correct new log category
I want an activity to log informational data to the Pega logfile. For that I created a new log category and used the content of element JavaClassName (in View XML of the activity) in the 'Loggers' field (in my case the value is: Rule_Obj_Activity_Rule_RuleSet_Name_OpruimenLegeRulesetsOokDieZonderRulesetVersie010101_Action_20250818T102526_910_GMT). In Admin Studio I set the Current log level to INFO (so both Default and Current log level are INFO) In de activity I use Log-Message method en also there I set the log level parameter to INFO (also tried 'Info')
But still the log line is not poppin up in the Pega log. The only way it works when I use parameter value 'InfoForced' in stead of 'Info' . But this not what I want: it should work with value 'Info' or am I wrong?
Why is it not working?
- Yes: I double checked if I have entered the correct value in the 'Loggers' field (since JavaClassName changes all the time you check-out/check-in)
- Yes: I double checked if I used the correct filter on de logfile (I see de logline when log level is InfoForced)
ai4process ltd
GB
This behaviour could be caused by Java class name mismatches or log level propagation issues. The value used in the “Loggers” field (e.g., Rule_Obj_Activity_...) changes with each check-in. If the logger is tied to a specific Java class name, it may become stale after updates.
Also, even if Admin Studio shows INFO as the current level, the logger may not be correctly initialized or mapped. InfoForced bypasses logger filters and writes directly to the log. Hence if you use InfoForced, irrespective of the log level, you should be able to see the log in the pega log file.
Could you please check if the JavaClassName that you retrieved from your xml is retrieved when the Rule is in check out state or it is in checked-in state as the JavaClassName changes whenever you checkout/ check in.
If you are using the log for debug, you can temporarily use InfoForced in your log activity but usually it is not recommended to have infoForced logs in Production.