User action types
The duration of a user action is called the ”action duration”. This represents the amount of time that the user waits until it’s possible for them to continue. This means that a low action duration (i.e., response time) is better than a high action duration.
There are different kinds of user actions:
A page load is represented as a single user action, such as a user entering a URL into a browser’s address bar. The start time of the user action begins with the W3C
XMLHttpRequests are started by an onload handler, the user action ends when the
XMLHttpRequest is complete.
In Web 2.0 applications, when a user interacts with a web site, some actions may cause an incomplete page reload. For example, a user might click a Search button that triggers an
XMLHttpRequest are pure client-side actions and don’t count as user actions. The start time of the user action is the time of the event. The end time is the end of the last
onreadystatechange event that is triggered by the
XMLHttpRequest. If an
XMLHttpRequest triggers additional
XMLHttpRequests, they are considered to be part of the same user action.
Custom user actions
User action naming rules
Many applications allow users to accomplish the same goal through different UI controls. When monitoring such applications it can be difficult to differentiate between actions that are slightly different though essentially the same. Likewise, if the UI of a application is translated into multiple languages, the same application function or control may appear under varying names. With user action naming rules, Dynatrace can detect such subtle variations and intelligently group related user actions into logical groups for monitoring.
Note: Dynatrace automatically removes certain common
sessionid tokens from user action names (for example,
jsessionid for Java containers, the default
sessionid for PHP, and
CFTOKEN for ColdFusion). Nonetheless, there are numerous session ID variations that may be present in your environment. If Dynatrace doesn’t automatically recognize and remove session IDs from certain user action names you encounter, you’ll need to configure custom naming rules for those user actions.
To configure naming rules for user actions, go to Settings > Monitoring overview > Applications and select your application. Then go to User actions to configure settings related to user action and URL detection.