Question
Pegasystems Inc.
US
Last activity: 22 Feb 2016 19:51 EST
Setting up Dynatrace UEM with Pega
My client is using it using Dynatrace User Experience Monitoring (UEM) for capturing performance metrics from the user's perspective. More information on Dynatrace can be found here -> http://www.dynatrace.com/en/index.html
My client is using it using Dynatrace User Experience Monitoring (UEM) for capturing performance metrics from the user's perspective. More information on Dynatrace can be found here -> http://www.dynatrace.com/en/index.html
The following line is the injected HTML that load the .js file:
<scripttype="text/javascript"src="dtagent61_n_8305.js"data-dtconfig="rid=RID_-516616792|rpid=-166556324|tp=500,50,0|reportUrl=dynaTraceMonitor">Issue we are facing
While watching the traffic through fiddler, we see the above script injected when the traffic hits the webserver. This HTML gets stripped out at some point in the transaction (in the application tier) and the browser never loads the .js file. This is causing dynatrace not to capture any of the metrics it is supposed to.
Accepted Solution
Pegasystems Inc.
US
Fortunately, the issue is fixed! DynaTrace released a fixpack that fixes the way the Javascript Agent works with Pega.
The version of dynaTrace before the fix-pack was Proprietary information hidden5. The version POST-FIX-PAC is Proprietary information hidden3.
JVM : 8.5.5
Naveen Soma can you help Prashant with this?
Pegasystems Inc.
US
can you attach the fiddler trace? Also does this work without webserver? i.e., direct access to prpc. Sometimes, webserver will inject certain js and break the prpc. Just want to make sure that is not the case.
Pegasystems Inc.
US
Kevin,
Not sure what you mean by "with out web server". The only way we have tried so far is to provide the PRPC web URL in Dynatrace. For eg - https://domain/prweb/prservlet.
BTW, I have attached the fiddler trace to my original post.
Pegasystems Inc.
US
What I mean by that is your topology of the system, e.g., is there a proxy server/load balancer/web server involved before the Websphere application server. These are pretty common in the real enterprise setup. I have to say that I do not have any experience on dynatrace UEM, so really cannot give you detailed guidance. Maybe someone else has done that can shed some lights. But if I were setting up myself, I would try UEM with simplest setup (not realistic but starting from simple case), i.e., direct access app server. Just by glancing your fiddler trace, I am pretty sure, you are going through some sort of web server through https (with plugin to Websphere application server).
Pegasystems Inc.
US
Hi Kevin,
Dynatrace eventually will need to be set up in production which will of course have a load balancer. However, I have asked the Dynatrace expert to try in an environment which doesn't have a load balancer to rule out the possibility that it is causing the issue.
Accepted Solution
Pegasystems Inc.
US
Fortunately, the issue is fixed! DynaTrace released a fixpack that fixes the way the Javascript Agent works with Pega.
The version of dynaTrace before the fix-pack was Proprietary information hidden5. The version POST-FIX-PAC is Proprietary information hidden3.
JVM : 8.5.5