Detailed web path information for a variety of metrics is presented in the web path performance charts. In addition to the information provided in the charts, you can compare web path performance, you can view details of a specific test, and you can review web path events that have occurred.

Web path performance

Web path performance charts provide historical performance information for each web path you create.

View web path performance charts

You can access the web path performance history from either the Web Paths page, the Web App Groups page, or the Web Dashboard page. By default, the last hour of data is displayed in the charts.

To view the web path performance history from the Web Paths page:

  1. Navigate to Experience > Web Paths.
  2. Find the web path you are interested in.
  3. Click the web path you want to view.

To view the web path performance history from the Web App Groups page:

  1. Navigate to Experience > Web App Groups.
  2. Expand the web app group containing the web path you want to view.
  3. Click the web path you want to view.

To view the web path performance history from the Web Dashboard page:

  1. Navigate to Experience > Web Dashboard.
  2. Click the web dashboard you are interested in.
  3. Expand the web app group containing the web path you want to view.
  4. Click the web path you want to view.

Web path performance charts

The Test Timeline page displays a number of historical charts that provide different views into the performance history of a web path over the selected time period. These include:

End User Experience chart

The End User Experience chart shows the total time needed to complete the script associated with the web path. In addition:

  • The total time is divided into the time taken by the network, the server, and the browser.
  • Changes in monitoring configuration are marked by a vertical grey bar.
  • A marker is placed on the timeline where results violate or clear a condition in the web path alert profile. Hover over the marker for event details.
  • Hover over the chart and click a blue pip to see the results of a single script execution (web test).
  • The pie chart shows the average over selected time period.

Milestone Breakdown chart

The Milestone Breakdown chart shows the total time needed to complete the script associated with the web path. In addition:

  • The total time is divided into the time taken by each milestone in the script.
  • Changes in monitoring configuration are marked by a vertical grey bar.
  • A marker is placed on the timeline where results violate or clear a condition in the web path alert profile. Hover over the marker for event details.
  • Hover over the chart and click a blue pip to see the results of a single script execution (web test).
  • The pie chart shows the average over the selected time period.

Apdex Score chart

The Apdex chart shows the overall Apdex score. In addition:

  • The overall Apdex score is divided into the Apdex scores for each milestone in the script.
  • Changes in monitoring configuration are marked by a vertical grey bar.
  • Hover over the chart and click a blue pip to see the results of a single script execution (web test).

HTTP Throughput chart

The HTTP Throughput chart shows the total capacity of the path from the monitoring point to the target as well as an indication of the percentage of total capacity used by HTTP traffic generated by the script. If a large percentage of the total capacity is used by HTTP traffic it indicates that network capacity should be reviewed as it may be a source of web path performance issues. In addition:

  • Changes in monitoring configuration are marked by a vertical grey bar.
  • The pie chart shows the average over the selected time period.

Response Time chart

The Response Time chart shows the total response time (the time it takes to establish a TCP connection with the target and receive the first byte of data). In addition:

  • The total response time is divided into the response time taken by the network and the server.
    • Minimum network response time calculation for HTTP is: 2 * RTT.
    • Minimum network response time calculation for HTTPS is: 4 * RTT.
    • RTT (Round-trip time) is time from A to B and B to A.
      • For HTTP this is SYN to SYN-ACK (1 RTT) and ACK to first byte (1 RTT).
      • For HTTPS there are an additional two RTTs for the SSL handshake.
    • Server response time = Total response time - Network response time
  • Changes in monitoring configuration are marked by a vertical grey bar.
  • The pie chart shows the average over the selected time period.

Adjust chart timeline

You can adjust the chart timeline so that the charts display only the data for the period you are interested in. There are three ways to do this: using the zoom links, using the date and time selector, and using the timeline slider.

To adjust the chart timeline using the zoom links:

  1. Navigate to the Test Timeline page for the web path you are interested in.
  2. In the Zoom field within the Selected time range pane, click a predefined time range.
  3. Drag the slider to the date and time you are interested in.
    • The charts display the data for the selected period.

To adjust the chart timeline using the date and time selector:

  1. Navigate to the Test Timeline page for the web path you are interested in.
  2. In the date and time selector field at the top right of the Selected time range pane, specify the “from” and “to” date and time.
    • The charts display the data for the selected period.
    • Drag the slider to adjust the selected period.

To adjust the chart timeline using the timeline slider:

  1. Navigate to the Test Timeline page for the web path you are interested in.
  2. On the slider bar at the bottom of the Selected time range pane, drag the left bar to the start of the desired period and the right bar to the end of the desired period.
    • The charts display the data for the selected period.
    • Drag the slider to adjust the selected period.

Comparing web path performance

There are times when it is desirable to compare the performance of two or more web paths. You can compare selected web paths or all web paths belonging to a web app group. The most valid comparisons are those between web paths with a common source monitoring point, target web app, or workflow. Comparison views can be saved. Once saved, they can be run again. Finally, you can also delete a saved comparison view.

Compare web paths

To compare the performance of two or more web paths:

  1. Navigate to Experience > Web Paths.
  2. Find the web paths you are interested in.
  3. Select the web paths you want to compare.
  4. In the Action drop-down, click Compare.
    • A new comparison view is created.
    • Click > Save to save the comparison view.

Compare web paths in a web app group

To compare the performance of all web paths in a web app group:

  1. Navigate to Experience > Web App Groups.
  2. Click Action > Compare for to the web app group you are interested in.
    • A new comparison view is created.
    • Click > Save to save the comparison view.

Run a comparison view

Once you have saved a comparison view, you can run it again at any time.

To run a comparison view:

  1. Navigate to Experience > Comparison Views.
  2. Select > Run for the comparison view you are interested in.
    • The comparison view is run.

Delete a comparison view

To delete a comparison view:

  1. Navigate to Experience > Comparison Views.
  2. Select > Delete for the comparison view you are interested in.
    • The comparison view is deleted.

Web tests

Every time the script associated with a web path is executed, it is considered a web test. Over time, the results of these web tests form the web path performance history charts, but details of the individual tests can also be viewed on the Test Drill-down page.

View web test results

To view the results of an individual web test:

  1. View the web path performance history for the web path you are interested in.
  2. Select a time period that includes the test you are interested in.
  3. Hover over either the End User Experience chart, the Milestone Breakdown chart, or the Apdex chart, and click the blue pip for the test you are interested in.
    • The Test Drill-down page containing the following sections is displayed in a separate tab:
      • Timeline
      • JavaScript Errors
      • Resource list
      • Charts: Resource Timing, Performance, Domain, and Content

Using the Test Drill-down page

Once you have accessed the Test Drill-down page for the web test you are interested in, there are a number of ways to find the specific information you are looking for.

Select a section of the timeline

The data shown on the Test Drill-down page is based on the selected section of the Timeline at the top of the page. The selected section is indicated by two vertical black bars on the Timeline. By default, the entire Timeline is selected but this can be changed either by moving the selection bars manually or by choosing a milestone to view.

To change the selected section by moving the selection bars manually:

  1. Navigate to the Test Drill-down page you are interested in.
  2. On the Timeline, drag the left selection bar to the start of the selection.
  3. Drag the right selection bar to the end of the selection.
    • The results on the rest of the page are based on the section of the Timeline selected.

To change the selected section by choosing a milestone:

  1. Navigate to the Test Drill-down page you are interested in.
  2. On the Timeline, double-click the milestone you are interested in.
    • The selection bars surround the selected milestone.
    • The results on the rest of the page are based on the selected milestone.

Filter resources

Under the JavaScript Errors section of the Test Drill-down page is a list of resources downloaded by the web page or pages accessed by the script. This list can be filtered based on a search string, a predefined filter, or both.

To filter the resource list based on a search string:

  1. Specify the section of the script execution timeline you are interested in.
  2. In the Filter by… field, enter a case-sensitive search string.
    • Only the resources whose resource name contains the search string are listed.

To filter the resource list based on a predefined filter:

  1. Specify the section of the script execution timeline you are interested in.
  2. Select one of the pre-defined filters (All, HTML/Text, Javascript, CSS, Image, Flash, and Other).
    • Only the resources whose data type matches the filter are listed.

To filter the resource list based on a search string and a predefined filter:

  1. Specify the section of the script execution timeline you are interested in.
  2. In the Filter by… field, enter a case-sensitive search string.
  3. Select one of the pre-defined filters (All, HTML/Text, Javascript, CSS, Image, Flash, and Other).
    • Only the resources matching the search string and the filter are listed.

Sort resources

No matter how they are filtered, the resources can be sorted based on data in any of the columns in the resource list.

To sort the resource list:

  1. Specify the section of the script execution timeline you are interested in.
  2. Filter the resource list if desired.
  3. Click the heading of the column you want to sort by.
    • The resource list is sorted by the column you selected.
  4. Click the heading again to reverse the sort order.

View resource details

The resource list on the Test Drill-down page provides some high-level information but additional information is available.

To view resource details:

  1. Specify the section of the script execution timeline you are interested in.
  2. Filter the resource list if desired.
  3. Click the resource you are interested in.
    • Resource details appear under the Headers tab.
    • Click the Timing tab to view detailed timing information.

Understanding the Test Drill-down page

The Test Drill-down page provides test execution details and is broken down by milestone. The results shown on the page are based on the section of the Timeline that is selected (see Select a section of the timeline). The main sections of this page include:

  • Timeline - shows the timeline for the web test execution including the relative time for each milestone and any subsequent processing. In addition, information for each milestone is listed.
  • JavaScript Errors - lists any JavaScript errors that occurred on pages accessed during script execution.
  • Resource list - is a list of all web page resources (resources used to build the web page) accessed during script execution and identifies resource name, the request method used, the response status, the type of resource, its size, how long it took to download (latency), and a timeline showing a breakdown of the download time. Hovering over this timeline provides detail on the resource acquisition. Note that resources can be downloaded in parallel.
  • Resource Timing chart - represents the percentage breakdown of time required to acquire the page resources for the selected part of the timeline into the following phases:
    • Blocking - the time spent in a browser queue waiting for a network connection.
    • DNS lookup - the DNS resolution time; time taken to resolve a domain name in the URL. The DNS server must “look up” the IP address associated with the domain name.
    • Connecting - the time taken to establish a TCP connection with the web server.
    • Sending - the time required to send an HTTP request to the web server.
    • Waiting - the time spent waiting for a response (the first byte of information received) from the web server.
    • Receiving - the time required to read the entire response (receive all information, first byte to last byte) from the web server.
  • Performance chart - shows the amount of script execution time associated with the network, the server, and the monitoring point’s internal web browser. Given that many operations are typically occurring in parallel, at a given point in time, if we are waiting on the network, we count it as network time. If we are not waiting on the network but are waiting on the server, we count it as server time. If we are not waiting on the network or the server, we count it as browser time.
    • Network - the amount of script execution time associated with the network. This is comprised of two parts: the time it takes to establish a connection and send the resource request to the server, and the time between when the server transmits the first byte of the response and when the browser receives last byte of the response.
    • Server - the amount of script execution time associated with the web server. This is the time between the server receiving the request and transmitting the response (calculated as the time the first byte of the response is received by the browser minus one way network latency).
    • Browser - the amount of script execution time associated with the browser. This is the time the monitoring point’s internal browser must wait for a network connection and the time it takes to render the page after all the content is received (though browser rendering begins after the first byte is received). It is the time not attributed to the network or server.
  • Domain chart - shows the number of bytes received from the servers listed.
  • Content chart - shows the number of bytes received by content type. The content type is a broad category that includes many similar data formats, determined by the mime-type of the resource.

For a given request, the timings found on the Resource Timing and Performance charts can be aligned as follows:

appview_latency_etc.png

In general, the information on the Test Drill-down page can be used to determine where the most time is being spent during script execution. If you are having performance issues, identifying the elements that most negatively affect performance enables you to determine where the largest efficiencies can be gained. Keep in mind that some of these activities occur concurrently so making them more efficient may not result in significantly faster page load times.

Web path events

Each time a web path alert is generated, an Experience event is logged. You can view seven days of events for all web paths or for a specific web path.

View web path event details for all web paths

To view web path events for all web paths:

  1. Navigate to Experience > Events.
    • View historical web path performance information by clicking a web path in the Web Path Name column.
    • View detailed web test information by clicking an alert message in the Description column.

View web path event details for a specific web path

You can view events for a specific web path from either the Web Paths page, the Web App Groups page, or the Web Dashboard page.

To view web path events for a specific web path from the Web Paths page:

  1. Navigate to Experience > Web Paths.
  2. Find the web path you are interested in.
  3. Click the web path.
  4. Click the Events tab.
    • View detailed workflow execution information by clicking an alert message in the Description column.

To view web path events for a specific web path from the Web App Groups page:

  1. Navigate to Experience > Web App Groups.
  2. Expand the web app group containing the web path you are interested in.
  3. Click the web path.
  4. Click the Events tab.
    • View detailed workflow execution information by clicking an alert message in the Description column.

To view web path events for a specific web path from the Web Dashboard page:

  1. Navigate to Experience > Web Dashboard.
  2. Click the web dashboard you are interested in.
  3. Expand the web app group containing the web path you want to view.
  4. Click the web path.
  5. Click the Events tab.
    • View detailed workflow execution information by clicking an alert message in the Description column.