The User Action PurePaths dashlet represents all captured PurePaths that start in the browser. Use this to analyze user actions like page loading or button clicks. A user action PurePath begins at the start of an action like loading the https://www.dynatrace.com/en page. It contains all web requests to instrumented system components (web server, application server). You can analyze all actions that begin in the browser to track functional problems and user performance issues.
The dashlet is divided into upper and lower panes. The upper pane consists of the following tabbed views:
- PurePaths: A list of PurePaths, each with corresponding dashboard or dashlet filter, and basic information such as name, response time, and start time, for each PurePath.
- Contributors: A list of all contributing actions and methods of the selected PurePath. Colors represent contributors with the highest execution times. The selected contributor is represented in the tree in the lower part of the dashlet.
- Errors: All errors in the selected PurePath. Errors are defined by several rules. See System Profile - Error Detection for more information.
The lower pane consists of the following tabbed views:
- Tree: The sequential representation of all contributors in a tree.
- Transaction Flow: The PurePath contributing system components visualized in a transaction flow.
- API Distribution: Execution and CPU time distribution of the PurePath's contributing APIs.
The PurePaths View shows a list of all user action PurePaths that match the applied dashboard or dashlet filters such as timeframe or application. Each PurePath receives basic information such as name, start time and client IP.
- (Error) State: Error State of the PurePath (Failed Transaction, Error).
- (Internal) State: Current state of the PurePath. Find details about PurePath states here.
- PurePath: String representing the PurePath identifier.
- Domain: The requested domain.
- Duration: The total response time of the action, in milliseconds.
- Response Time: Total duration of PurePaths (in ms).
- Compare to performance baseline: Response time compared to performance baseline, configured for the application to which the PurePaths is assigned. See System Profile - User Experience for details.
- Server Contribution: Time that is spent on the server to process requests with an immediate impact on the user action response time.
- Network Contribution: Estimated time that was spent to transfer resources with an immediate impact on the user action response time.
- User Expreience: The user experience index (Satisfied, Tolerating, Frustrated).
- Client IP: IP address of the client that triggers the user action.
- Start Time: The time when the PurePath started.
- Sub-Requests: Number of web requests caused by the user action.
- Failed Transaction: Number of failed transactions in the PurePath.
- Location: Geographical location of the client that triggers the user action.
- Client Family: Client family of the client that triggers the user action.
- Tag ID: Any tag associated with the user action.
- Application: Application, where the PurePath is assigned. See System Profile - Applications for application configuration details.
- Bandwidth: The connection bandwidth.
- Action Group: The name of the action group used to calculate the user experience.
- Threshold: The action groups defined threshold, in milliseconds.
- Performance metric: The metric defined for the user action that is compared to the threshold.
- Performance value: The value of the metric being compared to the threshold, in milliseconds.
- Factor reason: The reason why the factor was applied to the user experience thresholds.
- Threshold factor: The factor that was applied to the user-experience thresholds, due to external conditions.
- Visually complete: The time at which page appears visually complete.
- Speed index: The average time when visible parts of the page display.
The User Action PurePaths dashlet calculates how much of the response time is split between the client, server and network time. The algorithm to calculate the three fractions works in the following way:
- Server time or server contribution: The sum of the calls to blocking APIs in server-side PurePaths, considering overlaps. Simply summing up the PurePaths durations (even considering overlaps) creates a wrong impression, since the network bandwidth influences the PurePath: Blocking writes on the server-side prolong the PurePath. A client's (browser's) slow network connection can prolong the PurePath.
- Network time or network contribution: The sum of all response sizes sent to the client / bandwidth of the client.
- Client time or client contribution: The rest of the user action response time is client time.
To calculate the network duration you must enable response size capturing and bandwidth detection. Response size capturing is disabled by default, but you can enable it in the Web server, Servlet or ASP.NET sensors. Bandwidth detection is disabled by default. To enable it click System Profile > User Experience. See System Profile for more information.
See PurePaths dashlet - Contributors tab for more information.
See PurePaths dashlet - Errors tab for more information.
The user action PurePath tree is rooted at the trigger of an action such as click on or loading of, and contains all web requests to instrumented web and application servers. Web requests within frames are grouped in a separate section at the bottom of the tree. The user action PurePath ends with the onLoad handler node, which shows the time spent in activities after the page is loaded.
To analyze single web requests, select a request in the tree and drill down to an applicable dashlet.
The Transaction Flow view shows the distribution of PurePaths over system components or tiers, monitored by distinct AppMon Agent instances. Components that are part of a selected PurePath execution are highlighted. PurePaths that span multiple components are represented by dashed lines between the components.
See PurePaths Dashlet - API Distribution tab for more information.