The User Actions dashlet shows information about performance, errors and affected visits. The lower pane displays a chart with response time distribution, or a list of specific user action requests.
User Actions list
UEM Metrics include Visits, Duration, End-To-End Response, User Action Performance, Apdex, Client Time, Server Time, and Network Time.
Default columns in the dashlet include:
- Name: Action name comprised of a user action and the page URL, or the caption of an element where the action was captured.
- Count: Number of occurrences for a user action.
- Visits: Number of visits that executed a user action.
- Duration[s]: Average duration of user actions. The action duration is calculated from the start time (for example, click, page load) until the triggered request is processed (for example, a new page is loaded) and includes asynchronous time.
- User Action Performance: User experience for a user action as calculated by the Apdex range. See Apdex for more information.
- Apdex: Apdex of user actions. An asterisk ( * ) indicates that the Apdex was calculated from a small number of samples (< 100). See Apdex for more information.
- Failed Actions: Rate of failed actions.
- Total Duration: Summarized duration of user actions.
- Server Contribution [s] or Server Time: Time spent on server to process requests that have an immediate impact on the user action response time.
- Client Contribution [s] or Client Time: Time spent on the client including user action, server time and network time. If you have not turned on bandwidth detection, the client time also contains the network time.
- Network Contribution [s] or Network Time: Estimated time spent on transferring resources that have an immediate impact on the user action response time.
Async Path 1
Async Path 2
Response Time: 100ms, because
doGet finishes after 100ms which means the transaction actually delivers the response back to the end user in 100ms.
Duration: 650ms. Assume that the two asynchronous paths start at the same time. The duration is 650ms, because the PurePath is completed (= last event received) after 650ms.
Execution Total: 1150ms. It takes1150ms to execute the transaction although some of it is executed in parallel.
You can analyze the user actions by different aspects. Use the different structure modes in the dashlet tool bar. Aggregate user actions by the following aspects:
- User Action: Aggregates User Actions by their action type (click, key press or load action). Page load actions are grouped further by the requested URI.
- ClientType, ClientFamily: Groups all user actions by client type (for example, desktop browser, mobile browser, and mobile app) and client family, with version or device information (for example, IE Mobile-IE Mobile 9.0, or Apple-iPod touch 4G). For example, a Mozilla Firefox 6 user action belongs in the Desktop Browser-Firefox-Firefox 6.0 group.
- Application: This is defined in the System Profile.
- URI (= uniform resource identifier) Title: The page title is used as grouping criteria.
- Visit: Groups all visitor user actions.
Response time charts
The lower pane of the dashlet provides two different response time charts. Response times are displayed as a histogram or are grouped by client family. These charts focus on the selected group of user actions and support multi-selection.
If you select a specific user action, the lower pane displays the list of web requests captured for the selected user action, instead of one of the response time charts.
Custom filtering and splitting
To filter and split an expression, click Custom Query on the toolbar . Filter expressions support a Java-like syntax. To split an expression, use a comma-separated properties list. Click CTRL + SPACE for a list of available filter and splitting values. You can store favorite filters and splittings for future use.
Expressions support a Java-like syntax. The following tables describe constants and operators recognized within expressions:
|||, |, or, OR||logic or|
|&&, &, and, AND||logic and|
|!=, <>||not equals|
|<, >, <=, >=||relational operators for smaller, greater, smaller than or equals to, and greater than or equals to|
|=~, ~=||matches a regular expression (right hand side is a regular expression)|
|!=~, !~=, <>~||does not match (right hand side is a regular expression|
|like, LIKE||SQL style string match function using '%' as joker character|
ClientFamily = Firefox and ClientFamilyVersion = %4%: Filters a Firefox browser's user actions with a version string that contains the character 4.
URI = %booking%: Shows only user actions with a URI that contains the phrase booking .
Country, Region, City: Groups user actions by a geographical location hierarchy that begins with the user's country.
OperatingSystem: Groups user actions by the detected operating system.