prlog4j2.xml file request GUID string changes not getting reflected in the PEGA logs.

Hi Team,

Below mentioned standard prlog4j2.xml pattern plus the request GUID string changes(Underlined) not getting reflected in the PEGA logs (PRPC731).

<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} [%X{AD.requestGUID}] - %m%n

GUID injection (for AppDynamics) would be required to View the Correlated Logs and business Transaction Data.

Please suggest if you need additional details.

Thank you.


Keep up to date on this post and subscribe to comments

August 16, 2019 - 6:03am


sanity check, have you confirmed that the prlog4j2.xml that you edited is the one being used? Maybe you can test a generic log4j appender with AppDynamics jars, completely independent of Pega platform.

August 16, 2019 - 11:56am
Response to KevinZheng_GCS

Edited prlog4j2.xml is the one in use.

"generic log4j appender with AppDynamics jars " It works fine independent of Pega platform.

Please let me know if a SR is required for obtaining quick/accurate solution/direction.

Thank you.

August 17, 2019 - 11:38am

Not yet, since most of the your exercise is on the appdynamics side. Can I suggest you try Pega log4j jar in your generic test (outside Pega, u said it works)? If this turns out not working, then go ahead with an SR, we will need to investigate the difference btw your log4j jar used in your generic test and that of Pega.

August 18, 2019 - 10:24am


Another point. I checked the appdynamics website, it says requestGUID injection support only for log4j and logback. In your generic test, did you use log4j or log4j2? It would be interesting to know. If for example, your test only works for log4j but not log4j2 (which Pega uses), then that explains the behavior.