Skip Headers
Oracle® Enterprise Manager Framework, Host, and Third-Party Metric Reference Manual
10g Release 2 (10.2)

Part Number B16230-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

8 Services Metrics

This chapter describes the Services Metrics.

8.1 DNS Response Metrics

The following sections lists the DNS Response metrics, their descriptions, and user actions.

User Action

If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.

8.1.1 [DNS] Number of Results

A response to a DNS request may contain multiple answers. This indicates the number of answers (e.g. the number of IP addresses) in the response from the DNS service.

User Action

If the number of results is not what it should be, then you will need to examine your DNS service's configuration.

8.1.2 [DNS] Status

Indicates whether the query was successful.

User Action

Consult the Results metric for details.

8.1.3 [DNS] Total Connect Time (ms)

Time taken to connect to the DNS service. This metric is collected for queries using the TCP protocol.

User Action

A slow Total Connect Time suggests that network congestion is a problem.

8.1.4 [DNS] Total Response Time (ms)

Total time required to receive a response from the DNS service.

User Action

Unusually slow response times can occur if the DNS server has to perform a lookup before it can respond. If the total response time is consistently slow, then either the network may be slow, or the DNS server may be having trouble generating a response. Try using traceroute to diagnose network issues

8.1.5 [DNS] TTL (seconds)

A response to a DNS request may contain multiple answers. Each answer in a DNS response has a TTL (Time To Live) that indicates the number seconds that the answer may be cached by a client. The TTL value reported here is the minimum TTL of all the answers in the DNS response.

User Action

If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.

8.1.6 DNS Results

The results of the DNS query. In the event of a status down, the reason for the status down will be displayed here.

8.2 FTP Response Metrics

The following table lists the FTP Response metrics and their descriptions.

Table 8-1 FTP Response Metrics

Metric Description

[FTP] Connect Time (ms)

Time taken to establish a connection with the FTP service.

[FTP] Download Rate (KB/second)

Rate at which the data is downloaded from the FTP service.

[FTP] Download Time (ms)

Total time taken to download a file from the service

[FTP] Login Time (ms)

Time required to login to the FTP service.

[FTP] NOOP Time (ms)

Time required to perform a NOOP. A NOOP ("No Operation") is a request that the FTP service respond with an "OK" status. A NOOP is similar to network round-trip time because generating a response to a NOOP requires minimal effort.

[FTP] Number of Retries

Number of retries required before the test was successful.

[FTP] Status

Indicates that all requests succeeded and that the downloaded file matched the uploaded file.

[FTP] Status Description

Details on the reason for any service failure.

[FTP] Total Time (ms)

The total time required to test the FTP service.

[FTP] Upload Time (ms)

Time taken to upload a file to the service.

[FTP] Upload Rate

Rate at which the data is downloaded from the FTP service.


8.3 HTTP Raw Metrics

The following sections lists the HTTP Raw metrics, their descriptions, and user actions.

8.3.1 HTTP Raw Time Per Connection

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.

User Action

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.

8.3.2 HTTP Raw Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the transaction, step or step group. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

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.

8.3.3 HTTP Raw Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

8.3.4 HTTP Raw Connect Time (ms)

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.

User Action

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.

8.3.5 HTTP Raw First Byte Time (ms)

This is the First Byte Time divided by the number of pages in the step, step group, or transaction.

User Action

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.

8.3.6 HTTP Transaction DNS Time

This metric is not supported for this version of Enterprise Manager.

8.3.7 HTTP Raw HTML Time (ms)

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.

User Action

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.

8.3.8 HTTP Raw Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

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.

8.3.9 HTTP Raw Perceived Slowest Page / Page Element Time (ms)

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.

User Action

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.

8.3.10 HTTP Raw Perceived Time per Page / Page Element (ms)

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.\

User Action

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.

8.3.11 HTTP Raw Perceived Total Time (ms)

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.

User Action

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.

8.3.12 HTTP Raw Redirect Time (ms)

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.

User Action

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.

8.3.13 HTTP Raw Status

Indicates whether the Web transaction was successful.

8.3.14 HTTP Raw Status Description

If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error.

8.3.15 HTTP Raw Total Time (ms)

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.

User Action

Use the Total Time Metric to identify problem transactions. After you identify a transaction that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

8.3.16 HTTP Raw Transfer Rate (KB per second)

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.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

8.3.17 HTTP Raw First Byte Time

Enterprise Manager breaks down each transaction, step or step group into individual phases. Performance metrics for each phase 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.

User Action

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.

8.3.18 HTTP Raw URL

This is the URL associated with the step.

8.4 HTTP Step Group Metrics

The following sections lists the HTTP Step Group metrics, their descriptions, and user actions.

8.4.1 [HTTP Step Group] Connect Time (ms)

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.

User Action

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.

8.4.2 [HTTP Step Group] Broken URL Count

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.

User Action

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.

8.4.3 [HTTP Step Group] First Byte Time (ms)

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.

User Action

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.

8.4.4 [HTTP Step Group] Broken URL Details

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

8.4.5 [HTTP Step Group] First Byte Time per Page (ms)

This is the First Byte Time divided by the number of pages in the step group.

User Action

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.

8.4.6 [HTTP Step Group] HTML Time (ms)

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.

User Action

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.

8.4.7 [HTTP Step Group] DNS Time

This metric is not supported for this version of Enterprise Manager.

8.4.8 [HTTP Step Group] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

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.

8.4.9 [HTTP Step Group] Perceived Slowest Page Time (ms)

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.

User Action

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

8.4.10 [HTTP Step Group] Perceived Time per Page (ms)

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.

User Action

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.

8.4.11 [HTTP Step Group} Perceived Total Time (ms)

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.

User Action

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.

8.4.12 [HTTP Step Group] Redirect Time (ms)

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.

User Action

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.

8.4.13 [HTTP Step Group] Status

Indicates whether the Web transaction was successful.

8.4.14 [HTTP Step Group] Status Description

If the beacon is unable to run the step group successfully, this metric returns a description of the error that prevented the step group from running.

8.4.15 [HTTP Step Group] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step group.

User Action

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.

8.4.16 [HTTP Step Group] Transfer Rate (KB per second)

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.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

8.4.17 [HTTP Step Group] Total Time (ms)

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.

User Action

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.

8.5 HTTP Transaction Metrics

The following sections lists the HTTP Transaction metrics, their descriptions, and user actions.

8.5.1 [HTTP Transaction] Connect Time (ms)

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.

User Action

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.

8.5.2 [HTTP Transaction] First Byte Time (ms)

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.

User Action

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.

8.5.3 [HTTP Transaction] First Byte Time per Page (ms)

This is the First Byte Time divided by the number of pages in the transaction.

User Action

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.

8.5.4 [HTTP Transaction] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

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.

8.5.5 [HTTP Transaction] HTML Time (ms)

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.

User Action

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.

8.5.6 [HTTP Transaction] Perceived Slowest Page Time (ms)

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.

User Action

Use this metric to identify problem pages. After you identify a page or transaction that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

8.5.7 [HTTP Transaction] Perceived Time per Page (ms)

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.

User Action

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.

8.5.8 [HTTP Transaction] Perceived Total Time

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.

User Action

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.

8.5.9 [HTTP Transaction] Redirect Time (ms)

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.

User Action

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.

8.5.10 [HTTP Transaction] Status

Indicates whether the Web transaction was successful.

8.5.11 [HTTP Transaction] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

8.5.12 [HTTP Transaction] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a transaction.

User Action

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.

8.5.13 [HTTP Transaction] Total Time (ms)

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.

User Action

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.

8.5.14 [HTTP Transaction] Transfer Rate (KB per second)

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.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

8.6 HTTP User Action Metrics

The following sections lists the HTTP User Action metrics, their descriptions, and user actions.

8.6.1 [HTTP Step] Connect Time (ms)

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. 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.

User Action

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.

8.6.2 [HTTP Step] Broken URL Count

This metric measures the number of errors encountered when displaying content for the pages accessed by the step. For example, missing GIF images or style sheets will increase the value of the Broken Count metric.

User Action

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.

8.6.3 [HTTP Step] Broken URL Content

This metric is not currently collected by Oracle Enterprise Manager and is for internal use only.

8.6.4 [HTTP Step] DNS Time

This metric is not supported for this version of Enterprise Manager.

8.6.5 [HTTP Step] First Byte Time (ms)

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 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.

User Action

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.

8.6.6 [HTTP Step] First Byte TIme per Page Element (ms)

This is the First Byte Time divided by the number of step elements.

User Action

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.

8.6.7 [HTTP Step] HTML Time (ms)

Enterprise Manager breaks down each step. 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.

User Action

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.

8.6.8 [HTTP Step] Non-HTML Time (ms)

This is the amount of time it takes to transfer the non-HTML content such as images to the browser.

User Action

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.

8.6.9 [HTTP Step] Perceived Slowest Page Element Time (ms)

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.

User Action

Use this metric to identify problem pages. After you identify a page or a step that is slow to respond to user requests, you can drill down and analyze each phase of the transaction to isolate and repair the problem.

8.6.10 [HTTP Step] Perceived Time per Page Element (ms)

The average amount of time that it would take a Web browser to play each 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. 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.

User Action

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.

8.6.11 [HTTP Step] Perceived Total Time (ms)

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.

User Action

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.

8.6.12 [HTTP Step] Redirect Time (ms)

Enterprise Manager breaks down each step into individual phases. Performance metrics for each phase of the step 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.

User Action

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.

8.6.13 [HTTP Step] Status

Indicates whether the Web transaction was successful.

8.6.14 [HTTP] Status Description

If the beacon is unable to run the transaction successfully, this metric returns a description of the error that prevented the transaction from running.

8.6.15 [HTTP Step] Time per Connection (ms)

This is the Connect Time divided by the number of connections made while playing a step.

User Action

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.

8.6.16 [HTTP Step] Total Time (ms)

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.

User Action

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.

8.6.17 [HTTP Step] Transfer Rate (KB per second)

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.

User Action

Slow transfer rate can be caused by network congestion or other connectivity issues.

8.6.18 [HTTP Step] URL

This is the URL associated with the step.

8.7 ICMP Echo Response Metrics

The following sections lists the ICMP Echo Response metrics, their descriptions, and user actions.

8.7.1 [ICMP Ping] Last Host

Indicates the last node that was reached successfully while traversing to the final destination.

User Action

If the last host is not your destination node, there may be an indication that network problems exist between the last host and the destination node. Validate that the host is up and that none of your routers are down.

8.7.2 [ICMP Ping] Number of Hops

Indicates the number of network nodes traversed to reach the host.

User Action

If this number is higher than you think it should be, examine your network configuration. Your routers may be routing packets improperly.

8.7.3 [ICMP Ping] Packets Dropped (%)

Indicates the percentage of packets that could not reach their destination.

User Action

Packets are usually dropped due to a congested network. Remove the source of the congestion or upgrade your network bandwidth.

8.7.4 [ICMP Ping] Response Time (ms)

Indicates the average amount of time that the agent waited before receiving a response for each "ping" sent to the host.

User Action

Slow response time could indicate that there is some network congestion or that a packet takes a long time to reach the host. Investigate your network configuration. When Response Time is high, the Number of Hops is usually also high.

8.7.5 [ICMP Ping] Status

Indicates that the host is reachable from the agent.

8.8 IMAP Response Metrics

The following table lists the IMAP Response metrics and their descriptions.

Table 8-2 IMAP Response Metrics

Metric Description

[IMAP] Connect Time (ms)

Time it took (in milliseconds) to open an IMAP connection

[IMAP] Login Time (ms)

Time it took (in milliseconds) to log into an IMAP Service

[IMAP] Status

Current status of the IMAP service, either Up, Down, Status Pending, or Agent Unreachable

[IMAP] Time to Read Email (ms)

Time it took (in milliseconds) to read an e-mail message

[IMAP] Time to List Folders (ms)

Time it took (in milliseconds) to list the e-mail folders

[IMAP] Timing (ms)

Total time it took (in milliseconds) to open an IMAP connection, log into the IMAP service, list the e-mail folders, and read an e-mail message


8.9 LDAP Response Metric

The following section lists the LDAP Response metric and its description.

8.9.1 [LDAP] Status

Shows the current status of the LDAP service, either Up, Down, Status Pending, or Agent Unreachable.

8.10 NNTP Response Metrics

The following table lists the NNTP Response metrics and their descriptions.

Table 8-3 IMAP Response Metrics

Metric Description

[NNTP] Connect Time (ms)

Time it took (in milliseconds) to open an NNTP connection

[NNTP] Status

Current status of the NNTP service, either Up, Down, Status Pending, or Agent Unreachable

[NNTP] Time to post news article (ms)

Time it took (in milliseconds) to post a message to the news group through the NNTP service

[NNTP] Total Time

Total time it took (in milliseconds) to open an NNTP connection, log in, retrieve a message and post a message to the news group

[NNTP] Time to retrieve news article (ms)

Time it took (in milliseconds) to retrieve a message from the NNTP service


8.11 OS Response Metrics

The following table lists the OS Response metrics and their descriptions.

Table 8-4 OS Response Metrics

Metric Description

[Custom Script] Number of Retries

Total number of retries before the script is successfully executed

[Custom Script] Status

Status of the service test. The test is successful of the return code of the script is 0.

[Custom Script] Total Time (ms)

Total time required to run the script

[Custom Script] Custom Metric 1

Numeric value should be generated for each line of the custom script. This column corresponds to the first line generated by the script.

[Custom Script] Custom Metric 2

Numeric value should be generated for each line of the custom script. This column corresponds to the second line generated by the script.

[Custom Script] Custom Metric 3

Numeric value should be generated for each line of the custom script. This column corresponds to the third line generated by the script.

[Custom Script] Custom Metric 4

Numeric value should be generated for each line of the custom script. This column corresponds to the fourth line generated by the script.

[Custom Script] Custom Metric 5

Numeric value should be generated for each line of the custom script. This column corresponds to the fifth line generated by the script.

[Custom Script] Custom Metric 6

Numeric value should be generated for each line of the custom script. This column corresponds to the sixth line generated by the script.

[Custom Script] Custom Metric 7

Numeric value should be generated for each line of the custom script. This column corresponds to the seventh line generated by the script.

[Custom Script] Custom Metric 8

Numeric value should be generated for each line of the custom script. This column corresponds to the eighth line generated by the script.

[Custom Script] Custom Metric 9

Numeric value should be generated for each line of the custom script. This column corresponds to the ninth line generated by the script.

[Custom Script] Custom Metric 10

Numeric value should be generated for each line of the custom script. This column corresponds to the last line generated by the script.


8.12 POP Response Metrics

The following table lists the POP Response metrics and their descriptions.

Table 8-5 POP Response Metrics

Metric Description

[POP] Connect Time (ms)

Time it took (in milliseconds) to open a POP connection

[POP] Login Time (ms)

Time it took (in milliseconds) to log into the POP service

[POP] Status

Current status of the POP service, either Up, Down, Status Pending, or Agent Unreachable

[POP] Time to Read Email (ms)

Time it took (in milliseconds) to read a short e-mail message

[POP] Timing (ms)

Total time it took (in milliseconds) to open a POP connection, log in, and read a short e-mail message


8.13 Port Checker Metrics

The following sections list the Port Checker metrics, their descriptions, and user actions.

8.13.1 [Port Checker] Status

Indicates whether agent could successfully connect to the Expected Open Ports or it could not connect to the Expected Closed Ports.

8.13.2 [Port Checker] Unexpectedly Closed Ports

Set of ports that were unexpectedly closed.

User Action

Check that there is no firewall blocking these ports. Check that the server listening on these ports is up.

8.13.3 [Port Checker] Unexpectedly Open Ports

Set of ports that were unexpectedly open.

User Action

If you have a firewall blocking these ports, check your firewall configuration.

8.14 SMTP Response Metrics

The following table lists the SMTP Response metrics and their descriptions.

Table 8-6 SMTP Response Metrics

Metric Description

[SMTP] Connect Time (ms)

Time it took (in milliseconds) to open an SMTP connection

[SMTP] Status

Current status of the SMTP service, either Up, Down, Status Pending, or Agent Unreachable

[SMTP] Time To Send Email (ms)

Time it took (in milliseconds) to send a short e-mail message

[SMTP] Total Time (ms)

Total time it took (in milliseconds) to open an SMTP connection and send a short e-mail message


8.15 SOAP Response Metrics

The following sections list the SOAP Response metrics and their descriptions.

8.15.1 SOAP Response Time

Time taken by the beacon to complete the entire operation. This includes the time taken to send the HTTP request and receive the response.

8.15.2 SOAP Response Response Time (ms)

Time taken by the beacon to complete the entire operation. This includes the time taken to send the HTTP request and receive the response.

8.15.3 SOAP Response Status

This can be 0 (status down) or 1 (status up). The status is down when there is any error detected by beacon while performing the operation. The Status may be down in following cases:

  • Due to any HTTP error

  • No HTTP errors but due to a SOAP fault in the response

8.15.4 SOAP Status

This can be 0 (status down) or 1 (status up). The status is down when there is any error detected by beacon while performing the operation. The Status may be down in following cases:

  • Due to any HTTP error

  • No HTTP errors but due to a SOAP fault in the response

8.16 Oracle SQL Response

The following sections list the SQL Response metrics, their descriptions, and user actions.

8.16.1 [SQL] Close Time (ms)

Time taken to close the connection.

User Action

Close Time might be slow if the network performance is slow. Examine your network configuration.

8.16.2 [SQL] Connect Time (ms)

Total time taken to connect to the database.

User Action

Connect Time might be slow if the network is congested, if the database is having trouble authenticating the user, or if the database is having trouble allocating connections. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.3 [SQL] Execute Time (ms)

Time taken to execute the SQL statement.

User Action

Execute Time will be slow if the database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.4 [SQL] Fetch Time (ms)

Time taken to retrieve data from the server.

User Action

Fetch Time might be slow if the network bandwidth is low or if database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.5 [SQL] Fetch Time per Row (ms)

Time taken to fetch each row (Fetch Time / Number of Rows Fetched). Fetch Time per Row is a good metric to use for setting thresholds and for comparing the performance of different Oracle SQL Timing tests.

User Action

Use the Fetch Time per Row metric to identify data transfer problems. If the value of this metric is high, then the data-transfer bandwidth between the client and the database is poor. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.6 [SQL] Number of Rows Fetched

The total number of rows fetched during a query.

User Action

If the Number of Rows Fetched is not what you expected, then examine the contents of your database. Unexpected rows in the result could affect Fetch Time and Total Time.

8.16.7 [SQL] Prepare Time (ms)

Time taken to prepare the SQL statement. This usually includes fetching metadata for the object types in the query.

User Action

Prepare Time might be slow if the network performance is slow or if database performance is slow. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.8 [SQL] Status

Indicates whether the SQL or PL/SQL statement could be successfully executed.

8.16.9 [SQL] Status Description

Provides a description of the status.

8.16.10 [SQL] Total Time (ms)

The total time taken to connect to the database and run the query. It is the sum of Connect Time, Prepare Time, Execute Time, Fetch Time and Close Time.

User Action

Use the Total Time metric to identify database connectivity problems. Examine the other metrics to isolate and repair the problem. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.16.11 [SQL] Total Time per Row (ms)

Time taken to perform the entire test divided by the number of rows fetched (Total Time / Number of Rows Fetched). Total Time per Row is a good metric to use for setting thresholds and for comparing the performance of different Oracle SQL Timing tests.

User Action

Use the Total Time per Row metric to identify database connectivity problems. As with the Total Time metric, you should examine the other metrics to isolate and repair the problem. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database.

8.17 TNS Ping Response

The following sections list the TNS Ping Response metrics, their descriptions, and user actions.

8.17.1 [TNS] Average Response Time (ms)

Indicates whether the database responds to the pings.

8.17.2 [TNS] Pings Dropped (%)

Indicates the percentage of pings that did not receive a response.

User Action

Check that the network is not congested and that the database is not under heavy load. If you have an Enterprise Manager target instance for the database, you should consult the homepage for the database

8.17.3 [TNS] Status

Indicates whether the database responds to the pings.