AppDynamics with PRPC using URL Obfuscated / Encryption
Has anyone used the Appdynamics business transaction monitoring in an implementation of prpc that is utilizing encryption and obfuscation: initialization/urlencryption value="true"
initialization/SubmitObfuscatedURL value="required" , This prevents the usage of the URL to determine the business call (ie. SubmitCase, etc. ) Example if finding out what the average business type #transactions are occurring during a given period , if it is slowing down or hitting a peak, so that we can compare that with the memory/cpu performance, etc?
***Edited by Moderator Marissa to update platform capability tags; update SR Details****
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 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.
This is a technical impossibility. App Dynamics monitors the URL for a page to determine performance. In Pega, pages are composed dynamically. The Pega URL does not include any details of the page being rendered, so the monitoring that App Dynamics performs will not provide any data about performance.