Hi, Can someone help me to find the loggername for function rule since I am unable to find logs in pegarules log.I would like to set them to debug .
Thanks.
Rashmitha
Hi, Can someone help me to find the loggername for function rule since I am unable to find logs in pegarules log.I would like to set them to debug .
Thanks.
Rashmitha
@RashmithaM Open the Rule Utility Function and use Actions > View XML to copy its pzInsKey (include the parameter list shown there).
In Admin Studio, go to Resources > Log categories and create a new log category.
Add that pzInsKey as the logger in the category, set the category level to DEBUG, and save.
Run the rule that calls the function again.
Now the function’s oLog messages will show up in PegaRULES.log, and DEBUG lines will appear because the logger is set to DEBUG.
Make sure you check the PegaRULES.log from the node that actually processed your request.
@Sairohith I did this and checked logs on all the nodes not only the requested node but I am still not able to view them.Also, will it make any difference calling the function from a when rule. Should I add logs to when rule as well?
Any suggestions on this would be really helpful. We are calling function inside a when rule. I tried adding logger for when rule as well but still I am unable to view logs.
Search for Rule_Alias_Function in the logger to select the correct function rule as per your requirements
Hello @RashmithaM
If the function you are trying to trace has oLog statements, then you can try to add below entries in the logger
com.pegarules.generated.converse_converselib - This is for any custom library
com.pegarules.generated.pega_rulesengine_utilities - This is for OOTB library
This will ensure that all the functions in that library will be logged according to the configuration you have provided in the logger category, provided it has oLog entries in it.
You can set ALL level as well. It will log all types of logs.
Sample execution below for both custom and OOTB libraries.
![]()
Hope this helps
Regards
JC
Thank you Jayachandra for the response, I tried adding these loggers as well but still unable to see logs . We called function inside a when rule and I see in the tracer the when rule is evaluated but oLog.infoforced statements are not visible in logs.
there is a bug in pega 24.1.4 version and they have provided following details
we have identified that this logging issue is related to a known defect in Pega Platform 24.1.4 affecting containerized Cloud deployments. The issue stems from a logging framework bug that prevents log entries from displaying correctly, causing them to merge together or be truncated. This affects all logging operations across the platform, not just specific rule types.and Pega provided a hotfix .
After installing HFIX-D1063, We are able to see the logs.
Thanks Rashmitha for the update