Possible to cache/deliver dtagent-xxx.js via CDN?
One of my customer notice a significant delay while UEM enabled, after some investigation I believe this is truly network related. The customer only see the latency for their customers from Asia, Singapore in particular. Here is the customer’s deployment and our observation.
Customer’s deployment:
Application server: hosted in one centralized DC in the States, with dynaTrace instrumentation and UEM enabled.
Content server: hosted by CDN.
Symptom:
- For contents delivered via CDN, components load time are similar for users from New York and Singapore.
- For contents delivered by the application server, from Singapore components load times is 10 times higher than from New York.
- Given a content of 2.5k delivered by application server directly, the component load time is almost the same as dtagent-xxx.js (15.6k) when hitting from Singapore, only 80ms shorter than dtagent-xxx.js. So I think migration to 6 will not help a lot.
Given the observation above, the customer want to know if it’s possible to get dtagent-xxx.js cached or delivered via CDN, Anyone has any practice to share on this topic please? Thanks!
Best Regards,
Flora
The answer is YES. dtagent.js is just a JavaScript library - so you can cache it on a CDN just as any other JavaScript file
Thank you Andrea!
Are there any steps we can follow to get this done?
I guess you just need to tell your CDN to also cache the dtagent.js file. I would talk with your CDN folks - I am sure they know what needs to be done to cache this type of content.
Andreas,
My customer copied the uem dtagent on the CDN, and now they can access the dt agent from cdn manually, but UEM is not able to pick it up. They even tried to specify the agent location as the cdn url but no luck. Any thoughts? Thanks!
You need to make sure that the /dynaTraceMonitor signal is sent back to the "root server". The dtagent.js will collect data in the browser and will send the collected data back on the configured URL - by default this is /dynaTraceMonitor. Naturally this request will also end up at the CDN. Therefore you need to configure the CDN to forward this request to the web server that contains the web server agent. So - this should just be a matter of correctly configuring the CDN
If the CDN has to forward this request back to the web server, how it would reduce the latency per say?
Originally we are thinking about putting dtagent-xx.js over CDN mainly because of the network latency we are seeing in the waterfall chart while downloading the .js file from the web server.
Hi Flora,
I think Andi may be answering a different question. I think that you are saying the following - correct me if I'm wrong. You put the dtagent.js on the CDN, and can see it there. But when the users are getting pages sent to their browsers with the reference to the dtagent.js embedded in the page, you're seeing our agent being downloaded from the "home" server, not the CDN. Is that it?
Rob
Yes Rob, that's the right expression, you have any clue?
Andreas/Rob,
I managed to get the browser end retrieve dtagentxxx.js successfully, but I never seen the browser send back data via /dynaTraceMonitor since then, there are no POST /dynaTraceMonitor at all from the developer view within Chrome, anything broken out there?
Best Regards,
Flora
Just got it work after some configuration change on dynaTrace side!
What did you end up doing?
