This chapter describes the Web Application metrics.
The following sections lists the HTTP Content metrics, their descriptions, and user actions.
This metric measures the average connect time for all pages in the transaction. This is calculated as: Total Connect Time / Number of Connections Made. The Connect Time is one of the phases of a transaction that can help you isolate and fix response time problems.
The average connect time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.
This metric measures the average First Byte Time for all pages in the transaction. This metric is computed as: Total First Byte Time / Number of Requests Made (either to fetch HTML or content). The First Byte time is one of the phases of a transaction that can help you isolate and fix response time problems.
The average First Byte Time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.
A single transaction often accesses multiple Web pages. The Average Page Response metric calculates the average response time of the pages within a single transaction. This metric is calculated as: Total Transaction Time / Number of Pages in the Transaction. For example, if the transaction connects to four different Web pages, this metric will calculate the average response time for the four pages each time the transaction is run.
If a particular transaction continuously exceeds the Average Page Response threshold, use the Beacon Data page to test the transaction from other beacons and over a specific time period. Use this data to pinpoint any trends or specific beacons that generate the alerts. Display the Beacon Data page by clicking the value of a metric on the Transaction Performance Page.
The beacon name if the name of the beacon for which the current metric data is being collected.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
This metric measures the number of errors encountered when displaying content for the pages accessed by the transaction. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.
Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.
This metric represents the estimated response time for a client such as a browser, to fetch all the pages in a transaction. The computed response time is calculated as if the contents of every page (such as images and HTML style sheets) were fetched in parallel using multiple threads.
Use the Calculated Response Time to predict the response time that will be experienced by your average end user.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the first phase of a transaction and represents the time it takes for a connection to the Web server to be established for all requests.
Slow connect time has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the Content Time, which is the amount of time taken to transfer page content to the browser. Page content includes images and style sheets, as opposed to the HTML coding for the page.
Consider reducing the size of images or other contents of the page
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.
As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser.
This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the total bytes of HTML code transferred from all the Web pages accessed by the transaction.
This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the number of HTML bytes when you compare the response time of your Web Application transactions.
This metric serves as a container for a set of metrics that provide you with information about the content of the Web pages you are monitoring, as well as response time information.
This metric is a container for a set of metrics you can use to measure the performance of your Web Application transactions. It indicates how quickly the pages respond to user requests.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content, for example.
Slow HTML time could indicate problems with your HTML coding. Check the source code for your Web Application page to see if there are ways to streamline or improve the logic of the HTML code.
This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the number of bytes that represent page content such as images and style sheets.
This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the total number of bytes when you compare the response time of your Web Application transactions. Pages with many images or complex style sheets will return a high value for the Page Content Bytes metric.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.
Significant time taken to redirect the HTTP request removes the possibility that the page content or the Web application software is causing a slow response time alert. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
A single transaction often accesses multiple Web pages. This metric indicates the maximum response time measured for a particular page within a transaction. The slowest page response time can be monitored for a specific transaction and from a specific beacon over a period of time.
You can set a threshold for this metric so that Enterprise Manager will generate an alert if the slowest page response for a particular transaction exceeds a value you specify when it is run from a specific beacon.
This metric returns a value of 1 if the selected beacon was successfully able to run the transaction for this Web application target.
There are several possible causes to a failed transaction. First, check the availability of the Web application and host for the Web application target.
Second, check the availability of the Oracle Agent for this beacon.
If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.
If you are reviewing the metric results from the All Metrics page, review the Value column of the Status Description table. The error description should offer clues about why the transaction failed.
This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the total number of bytes transferred from all the Web pages accessed by the transaction.
This metric can help you isolate the cause of any performance problems identified by this transaction. Be sure to consider the total number of bytes when you compare the response time of your Web Application transactions.
Total transaction time indicates the overall time spent to process the transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Content Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the total response time metric to identify problem pages. After you identify a page or transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The transaction name is the name of the transaction for which the current metric data is collected.
The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.
Slow transfer rate can be caused by network congestion or other connectivity issues.
The following sections lists the HTTP Step Group metrics, their descriptions, and user actions.
This metric measures the number of errors encountered when displaying content for the pages accessed by the step group. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.
Use this metric to measure the quality of the pages being served by your Web application. For example, high values for the Broken Count metric can indicate that files have been moved or that relative links in the application are broken.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.
Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.
This metric is not supported for this version of Enterprise Manager.
Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.
As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
This is the First Byte Time divided by the number of pages in the step group.
A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.
Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.
This is the amount of time it takes to transfer the non-HTML content such as images to the browser.
Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.
The amount of time that it would take a Web browser to play the slowest page in a step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem
The average amount of time that it would take a Web browser to play each page in the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.
Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.
The amount of time that it would take a Web browser to play the step group. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.
Enterprise Manager breaks down each step group into individual phases. Performance metrics for each phase of the step group can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step group. The time taken to redirect the request can affect the overall response time of the page.
Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.
If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.
This is the Connect Time divided by the number of connections made while playing a step group.
Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.
Indicates the overall time spent in processing the step group. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.
Slow transfer rate can be caused by network congestion or other connectivity issues.
The following sections lists the HTTP Transaction metrics, their descriptions, and user actions.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.
Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.
This metric is not supported for this version of Enterprise Manager.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.
As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
This is the First Byte Time divided by the number of pages in the transaction.
A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.
Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.
This is the amount of time it takes to transfer the non-HTML content such as images to the browser.
Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.
The amount of time that it would take a web browser to play the slowest page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The average amount of time that it would take a Web browser to play each page in the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.
Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The amount of time that it would take a web browser to play the transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.
Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.
If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.
This is the Connect Time divided by the number of connections made while playing a transaction.
Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.
Indicates the overall time spent to process the transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the Total Time Metric to identify problem transactions. After you identify a r transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.
Slow transfer rate can be caused by network congestion or other connectivity issues.
The following sections lists the HTTP User Action metrics, their descriptions, and user actions.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spend connecting for requests that result in redirects count as Redirect Time rather than Connect Time.
Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.
Enterprise Manager breaks down each step into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the First Byte Time, which is the total time taken between the last byte of the request sent and the first byte of the response received by the server for all requests made. This includes the network latency and the time for the server to respond.
As with the Connect Time and Redirect Time, this metric can help you pinpoint whether or not the page content or Web application software is causing the slow response time, as opposed to the actual time it takes to transfer one byte of information to the browser. A high First Byte Time suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
This is the First Byte Time divided by the number of step elements.
A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.
Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.
This is the amount of time it takes to transfer the non-HTML content such as images to the browser.
Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.
The amount of time that it would take a Web browser to play the slowest step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem
The average amount of time that it would take a Web browser to play each page in a step. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.
Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the step group to isolate and repair the problem.
The amount of time that it would take a Web browser to play the step element. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem transactions. After you identify a step group that's slow to respond to user requests, you can drill down and analyze each phase of the step to isolate and repair the problem.
Enterprise Manager breaks down each step element. Performance metrics for each step element can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a step. The time taken to redirect the request can affect the overall response time of the page.
Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.
If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.
This is the Connect Time divided by the number of connections made while playing a step element.
Slow Time per Connection has nothing to do with the content of the page itself. It is likely caused by a slow network or a busy Web server, which prevents the request from getting to the Web server in a timely manner. Transactions that use HTTPS will typically have a much higher Time per Connection than transactions that use HTTP.
Indicates the overall time spent in processing the step. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.
Slow transfer rate can be caused by network congestion or other connectivity issues.
The following sections lists the HTTP Raw metrics, their descriptions, and user actions.
This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction, step or step group can help you pinpoint the cause of a slow response time alert. Connect Time is the total time spent in the transaction connecting to the server. There may be multiple connections made during a transaction. Time spent connecting for requests that result in redirects count as Redirect Time rather than Connect Time.
Significant Connect Time values are usually caused by a slow network or a busy Web server. Significant Connect Time values may also indicate that there are too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.
This is the First Byte Time divided by the number of pages in the step, step group, or transaction.
A high First Byte Time per Page suggests that there may be high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.
Enterprise Manager breaks down each step, step group, or transaction into individual phases. Performance metrics for each phase can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.
Slow HTML time could indicate that the application is taking a long time to finish generating each page. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low.
This is the amount of time it takes to transfer the non-HTML content such as images to the browser.
Slow Non-HTML time could indicate that the application is taking a long time to generate images. Alternatively, slow HTML time could indicate that network bandwidth between the agent and the service is low. Consider reducing the number of distinct images in the application.
The amount of time that it would take a web browser to play the slowest page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be.
Use this metric to identify problem pages. After you identify a page or transaction that's slow to response respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
The average amount of time that it would take a Web browser to play each page in the step, step group, or transaction. This is a good metric for setting thresholds because it is the closest active measurement of what the user-experience is likely to be. Because it is normalized on a per-page basis, Perceived Time per Page is also a good metric for comparing the relative performance of different transactions.
Use this metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the step / step group / transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the Total Time Metric to identify problem transactions. After you identify a transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.
Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. Some pages automatically redirect the HTTP request to another page. Redirect time represents the total time of all redirects within a transaction. The time taken to redirect the request can affect the overall response time of the page.
Significant time taken to redirect the HTTP request. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.
If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error that prevented the transaction from running.
This metric measures the average connect time for all pages in the transaction. This is calculated as: Total Connect Time / Number of Connections Made. The Connect Time is one of the phases of a transaction that can help you isolate and fix response time problems.
The average connect time, when reviewed over a period of time, can indicate whether network congestion or other connectivity issues are the cause of poor Web application response time.
The transfer rate indicates how quickly data is being transferred from the Web server to the client browser. This is computed as: Total Kilobytes Received / Total Transaction Time.
Slow transfer rate can be caused by network congestion or other connectivity issues.
Indicates the overall time spent to process the step, step group, or transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, First Byte Time, HTML Time, and Non-HTML Time. This metric calculates total transaction time by assuming all contents of a page are fetched in a serial manner.
Use the Total Time Metric to identify problem transactions. After you identify a r transaction that's slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.