Dynatrace Real User Monitoring relies on browser cookies to correlate user interactions in the browser (i.e., user actions) with general page and backend performance metrics.
To track user-initiated transactions across the tiers of your application, Dynatrace uses the
x-dynatrace HTTP header.
To track transactions across the tiers of your application that are initiated by user actions, Dynatrace adds the
x-dynatrace header to all HTTP requests.
Cookies are used to:
- Monitor site performance
- Analyze website usage
- Track user behavior
HTTPOnly flag. Cookies must be included with each request so that user actions can be correlated with backend performance.
You can use the
Secure cookie flag, however this leads to loss of visibility into any unencrypted HTTP communication.
The following table provides an overview of cookie usage in Dynatrace.
|dtCookie||<randomValue> | <encoded application info>||session||100B|
|dtLatC||Measured latency to server||session||5B|
|dtSa*||<URL-encoded action name>||session||max URL length|
|rxvt||<timestamp> | <timestamp>||permanent||27B|
dtSa cookie is used to save user action names, such as
sessionStorage to store a backup of
dtCookie because certain browsers delete random cookies when too many cookies are used. Dynatrace sets the following two keys (see the table above for examples):
localStorage. The following table gives an overview of the key/value pairs that Dynatrace writes to local storage.