End User Experience Metrics dashlet
For example, the following images display two instances of the dashlet: request name by Ajax end-to-end time, and request name by page load time:
The first line graph shows that for some requests, the Ajax end-to-end time slowed down over the last half hour. The circle chart shows the distribution of the requests out of the total number of requests.
The second line graph shows that the page load time is higher for a certain request name, but the number of requests is insignificant, so it can be safely ignored.
Several dashlet instances can sometimes help you identify correlations between attributes and metric times. In this example, no correlation is directly noticeable.
This topic presents the following information about this dashlet:
Understanding the dashlet data
Attributes and metrics
For a selected attribute, you can examine up to ten of the most commonly used results, or up to ten of the slowest results. A dashed gray line on the graph shows the average time of the selected attribute.
The following table provides a description of each attribute. You can compare the distribution and performance of different types of the attributes.
Description of monitored attributes
Attribute | Description |
|---|---|
Ajax Domain | Domain names of the Ajax server |
Application Name | Monitored web applications |
Bot/Human | Bot and human users |
Browser | Browser types |
Browser Engine | Browser engines (also called, layout engine) |
City | City names, depends the information in the IP address that is recognized by the geolocation database |
Client IP | Client IP addresses |
Continent | Continent names, depends on the information in the IP address that is recognized by the geolocation database |
Country | Country names, depends on the information in the IP address that is recognized by the geolocation database |
Device | Devices used to access the web application |
Language | Languages of the browser |
New/Returning | New and returning users |
Operating System | Users' operating systems |
Province | Province names, depends on the information in the IP address that is recognized by the geolocation database |
Referrer Domain | Source Domain from which users originated For example, you can view the distribution of links from different advertisers. |
Request Name | Request names, derived from the URL path and fragment |
Request URL | Entire request URLs, as received from the client browser |
Screen Resolution | Screen resolutions |
Server IP | IP addresses of the application server |
For each attribute, you can choose any metric for a part of the page load time. The following diagram displays the monitored metrics for page navigation timing events, in the order they occur.
End-user experience metrics for page navigation
Click to enlarge image.
The following table provides a description of the metrics.
Descriptions of end-user experience metrics for page navigation times
Item in | Name | Description |
|---|---|---|
1. | Page Load Time | End-to-end page response time, the entire time it takes to load the page, from initial request to the browser finishes processing the page |
2. | Page DNS Time | Time for the browser to complete the required domain lookup while retrieving a resource |
3. | Page TCP Time | Time for the browser to establish a connection with the server, including other time intervals such as SSL handshakes and SOCKS authentication |
4. | Page SSL Time | Time for the browser to perform the SSL handshake to secure the connection |
5. | Page Back-End Time | Time spent on server and network |
Network Time | Time spent on network between the client and server To see the server time, you must have an App Visibility agent for Java or .NET installed on the relevant servers. For details, see Getting-started-with-setting-up-applications-for-monitoring. | |
Server Time | Time spent on the web server, server applications, and databases To see the server time, you must have an App Visibility agent for Java or .NET installed on the relevant servers. For details, see Getting-started-with-setting-up-applications-for-monitoring. | |
6. | Time to First Byte (TTFB) | Time that the browser waits to receive the first piece of information |
7. | Page Download Time | Time for the browser to download response from server |
8. | Page Front-End Time | Time for the browser to process the critical rendering path of the request, including parsing, rendering, downloading sources, and executing JavaScript functions |
9. | DOM Processing to Interactive | Time that the browser spends loading the web page until the user can start interacting with it |
10. | DOM Interactive to Complete | Time for the browser to load images and videos, and to execute JavaScript code that listens for the DOMContentLoaded event |
11. | Onload Time | Time for the browser to execute JavaScript code that waits for the window.load event |
12. | Ajax E2E Time | Time taken for the end-to-end process from the initial request to the browser receiving the Ajax content |
Working with the dashlet
- The circle chart shows the distribution of the total number of the selected attributes. The chart helps you see the percentage of the whole for the most used or slowest values
If the selected number of results is less than the total number, a gray area labeled Other is displayed. For example, if your ten slowest requests represent 25% of all requests on your application, the Other section of the circle chart helps you understand the ratio of the displayed requests to all requests. - To display a value on a graph, hover over the graph or anywhere in the circle chart. A tooltip shows the details
- To zoom in, drag over a section of the graph.
- To filter results, click an attribute in the legend. Although the line is not displayed on the graph, you can still see the attribute name and value.
The average line on the graph represents all the attributes, whether they are selected. - Set up a dashboard with several End User Experience Metrics dashlet instances to look for correlations with results.
- The dashlet updates values every minute.
Dashlet requirements
The End User Experience Metrics dashlet requires end-user application monitoring with TrueSight App Visibility Manager.
The dashlet displays data for the selected dashboard time and application.
Ensure that you perform the following steps before creating the dashlet:
1) Ensure that the proxy server system meets all the recommended requirements. For more information, see System requirements for App Visibility Manager server components.
2) Ensure that you have more than one Elasticsearch cluster instance configured. For more information, see Preparing for the App Visibility server installation and App Visibility proxy installation or upgrade connectivity and cluster checks.
Configuring the dashlet
You can configure this dashlet when you add or edit a dashboard. Ensure that you add the dashlet to a column that is set to 75% wide or larger.
- Click Add Dashlet and select the End User Experience Metrics dashlet.
Click the Configure Dashlet
icon.
The title of the dashlet automatically comprises the selected parameters that you choose in the following steps. Every change to the parameters updates the name.- From the Attribute list, select the data type by which you want to break down the way users access the application.
- From the Metric list, select the page navigation time metric by which you want to evaluate the attribute.
- Enter the number of results you want to see, from one to ten.
- Select how you want to order the results: by the most used or by the slowest.
- Select the height of the dashlet row: 3X or 4X.
The value of X is approximately 100 pixels. The default height is 3X.
If you have more than six results for an attribute, 4X provides an optimized view of the legend under the graph. - (Optional) Enter or edit your own descriptive title for the dashlet.
Troubleshooting dashlet issues
A location attribute (country, city, continent, or province) is displayed as Unknown if the end user's IP address is private or otherwise not recognized by the geolocation database.