We are not maintaining any session persistence and are caching all content in front of the dispatcher (which is where the cookie is inserted), so I am unsure what use the dtCookie is going to be.
Because the cache issues conditional requests to the origin web server (OWS - dispatcher) and on receipt of a 304 will serve the content already in cache (not get a fresh copy from OWS), unless the page is being updated there will never be a new cookie inserted – all clients will get same cookie for page X – is this a problem?
I must add that the application is Adobe CQ5 and the dispatchers mentioned in the question below are actually apache webservers on which the dynatrace agent is installed.
Answer by Clemens F. ·
The dtCookie is used by dynaTrace to combine several user actions (e.g. page loads, XHR actions) to a visit. If the dtCookie is the same on one page for all users, all page loads and actions for this page will be combined in one visit. This would make the visit concept useless for your application.
I'd suggest rather storing the pages in the cache without dtCookie. The dtCookie will be generated via the first dynaTraceMonitor beacon from browser->web server, which will be unique for each browser then and result in valid visits.
hth,
Clemens
JANUARY 15, 3:00 PM GMT / 10:00 AM ET