Hello,

I don't have any firsthand experience with Appdynamics, but if it uses the URL to identify commonality, that won't work with URL Obfuscation/encryption turned on. If you need Appdynamics to monitor your traffic, you would probably have to do the URL encryption from some kind of a proxy and stick Appdynamics in between that and the PegaPlatform server.

Thanks,

Mike

Thanks for reading, I did in the end open a SR with Pega , and as mentioned - once url encryption is set, there will be no way of using the URL to identify transactions.   I will be exploring other options to see if there is the ability to track  utilizing pojo (plain old java objects) or jmx calls - A lot of investigating will be needed . I am still relatively new with Appd and learning more each day with prpc. AES appears to gather exceptions and alerts, which I could possibly utilize, but still not quite what I am looking for.  I will come back here and update when I find a solution that will work. 

Thanks! I linked this post to your SR to help our Support Engineers with troubleshooting if needed.