To function fully, the web server or Java Agents must recognize the following requests of a browser and deliver them to the browser.
<script href="/dtagent_xxx.js" />). You can configure it in the User Experience section of the System Profile dialog box. Use an absolute URL, if possible, because browser or any proxy servers should cache this file.
dtbwimg_x.jpg) used for bandwidth detection should go. The monitor uses the following query parameters:
app, flavor, format, referer, session, srvid, type, visitID, size, zip, va
The User Experience sensor uses the following HTTP headers:
x-http-client-ip(in this order): Determine the IP of the client (also for geo-locating). If none of these headers is set, AppMon uses the remote peer's IP address.
X-Forwarded-Host, X-Host, and
Host: Determine the page host domain (also for application autodetection).
x-dtinit: Set to coordinate UEM session id generation between agents.
X-dynaTrace-Application: Added by a proxyable agent (i.e. apache, nginx), containing the ID of the RUM application.
X-dynaTrace-RequestState: Used for tracking subpath tree depth.
X-dynatrace-Origin-URL: Used to preserve the "original" request URL in case of URL rewrites.
The Mobile Agent uses the following HTTP headers:
x-dynatrace: The mobile agent sets this header which is used by the correlation to link web requests correctly to user actions.
dtCookie: Session cookie used to identify user sessions. This cookie is valid as long as the browser process is running. Do not confuse this with HTTP-sessions of web applications or visits. Both usually have timeouts.
dtPC: Page context cookie used to link web requests to user actions.
dtLatC: Latency of monitor signals.
dtSA: Source action cookie. On browsers that do not support sessionStorage.
The Mobile Agent uses the following cookies:
dtAdk: Identifies hybrid app user sessions and merges the hybrid and native part into the same session.
dtAdkTag: Used by the correlation to link web requests from a hybrid application's web view to user actions.