|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
You can use Oracle Enterprise Manager to view performance and availability metrics for your Web applications. For more information, see "Introduction to Managing Web Applications" in the Enterprise Manager online help.
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 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.
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.
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. For more information, see "Monitoring Transaction Performance" in the Enterprise Manager online help.
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.
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.
Enterprise Manager breaks down each transaction into indivual 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.
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 client for all requests made. This includes the network latency and the time for the server to respond.
This metric provides information about the amount of data transferred during the selected transaction. For each transaction, this metric provides the total number of HTML coding transferred from all the Web pages accessed by the transaction.
Enterprise Manager breaks down each transaction into indivual 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 transfering images or other page content, for example.
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. For more information, see "Setting Transaction Intervals and Thresholds" in the Enterprise Manager online help.
This metric returns a value of 1 if the selected beacon was successfully able to run the availability 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. For more information, see "About Web Application Availability" in the Enterprise Manager online help.
Second, check the availability of the Oracle Agent for this beacon.
If the beacon is unable to run the availability 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. For more information, see "Displaying the Web Application All Metrics Page" in the Enterprise Manager online help.
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.
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.
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.
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.
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.
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. For more information, see "Monitoring Transaction Performance" in the Enterprise Manager online help.
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.
Enterprise Manager breaks down each transaction into indivual 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.
Enterprise Manager breaks down each transaction into indivual 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.
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.
Enterprise Manager breaks down each transaction into indivual 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 transfering images or other page content, for example.
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.
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. For more information, see "Setting Transaction Intervals and Thresholds" in the Enterprise Manager online help.
This metric (and its accompanying chart when you display the Metric Detail page) can help you identify what time of day the response time peaked for this particular transaction and this particular beacon. Understanding the load at particular times of the day can help you identify unexpected trends and plan for additional hardware or software resources.
This metric returns a value of 1 if the selected beacon was successfully able to reach the destination host or run the transaction for a 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. For more information, see "About Web Application Availability" in the Enterprise Manager online help.
Second, check the availability of the Management Agent for this Beacon.
If the beacon is unable to run the availability 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. For more information, see "Displaying the Web Application All Metrics Page" in the Enterprise Manager online help.
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.
