This chapter describes the Services Metrics.
This metric is a container for a set of metrics you can use to measure the performance of your Calendar Server (CalDAV) service.
This metric indicates the time taken (in milliseconds) to verify the calendar access of the CalDAV URL.
This metric indicates the time taken (in milliseconds) to add a calendar event.
This metric indicates the time taken (in milliseconds) to add a calendar task.
This metric indicates the time taken (in milliseconds) to connect to the CalDAV server.
This metric indicates the time taken (in milliseconds) to list the contents of the folder.
This metric indicates the time taken (in milliseconds) to delete a calendar task.
This metric indicates the time taken (in milliseconds) to delete a calendar task.
This metric indicates whether the transaction made thorough the CalDAV service was successful.
This metric indicates the total time to complete the transaction made through the CalDAV service.
This metric indicates the time taken to list the calendar events for a week.
The following sections list the DNS Response metrics, their descriptions, and user actions.
If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.
This metric indicates the total number of retries before a DNS lookup is successful.
User Action
If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.
This metric indicates a response to a DNS request may contain multiple answers. This indicates the number of answers (such as the number of IP addresses) in the response from the DNS service.
If the number of results is not what it should be, then you will need to examine your DNS service's configuration.
This metric indicates whether the query was successful.
Consult the Results metric for details.
This metric indicates the time taken to connect to the DNS service. This metric is collected for queries using the TCP protocol.
A slow Total Connect Time suggests that network congestion is a problem.
This metric indicates the total time required to receive a response from the DNS service.
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
This metric indicates 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.
If TTL values are low, then you may consider configuring your DNS service to allow caching for longer periods of time.
This metric is container for a set of metrics you can use to measure the performance of your FTP service test.
This metric indicates the time taken to establish a connection with the FTP service.
This metric indicates the rate at which the data is downloaded from the FTP service.
This metric indicates the total time taken to download a file from the service.
This metric indicates the 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.
This metric indicates the number of retries required before the test was successful.
The following sections lists the HTTP Raw 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 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.
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 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.
This metric indicates 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.
This metric indicates 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.
This metric 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.
This metric indicates whether the metric is collected for step, step group, or transaction.
If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error.
This metric 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 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.
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.
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.
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.
The following sections lists the HTTP Step Group metrics, their descriptions, and user actions.
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 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.
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 metric is not currently collected by Oracle Enterprise Manager and is for internal use only.
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 metric is not supported for this version of Enterprise Manager.
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.
This metric indicates 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
This metric indicates 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.
This metric indicates 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 step group successfully, this metric returns a description of the error that prevented the step group 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.
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.
This metric 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 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.
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.
This metric indicates 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.
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 metric indicates 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 is slow to 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.
This metric indicates 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.
This metric 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.
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.
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 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.
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 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.
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. 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 metric indicates 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.
This metric indicates 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 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.
This metric indicates 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.
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.
This metric indicates 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 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.
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 metric indicates the Connect Time divided by the number of connections made while playing a step.
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.
This metric 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 ICMP Echo Response metrics, their descriptions, and user actions.
This metric indicates the last node that was reached successfully while traversing to the final destination.
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.
This metric indicates the number of network nodes traversed to reach the host.
If this number is higher than you think it should be, examine your network configuration. Your routers may be routing packets improperly.
This metric indicates the percentage of packets that could not reach their destination.
Packets are usually dropped due to a congested network. Remove the source of the congestion or upgrade your network bandwidth.
This metric indicates the average amount of time that the agent waited before receiving a response for each "ping" sent to the host.
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.
This metric is a container for a set of metrics you can use to measure the performance of the IMAP service test.
This metric indicates the time it took (in milliseconds) to open an IMAP connection.
This metric indicates the time it took (in milliseconds) to log into an IMAP Service.
This metric indicates the current status of the IMAP service, either Up, Down, Status Pending, or Agent Unreachable.
This metric indicates the current status of the IMAP service, either Up, Down, Status Pending, or Agent Unreachable.
This metric indicates the time it took (in milliseconds) to read an e-mail message.
This metric indicates the time it took (in milliseconds) to list the e-mail folders.
This metric indicates the 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.
The following lists the JDBC response metrics and their descriptions.
This metric indicates whether the query made through JDBC connection went through successfully.
This metric indicates the total time taken to connect to the database through JDBC and run the query. It is the sum of connect time, prepare time, execute time, fetch time, and close time.
This metric indicates the total time taken to connect to the database.
This metric indicates the time taken to prepare the JDBC statement. This usually includes fetching metadata for the object types in the query.
This metric indicates the time taken to retrieve data from the server.
This metric indicates the total number of rows fetched during a query.
This metric indicates the time taken to perform the entire test divided by the number of rows fetched (Total Time/Number of Rows Fetched).
This metric is a container for a set of metrics you can use to measure the performance of your LDAP service test.
This metric indicates the time it took (in milliseconds) to perform an e-mail addressing search against an LDAP server.
This metric indicates the time it took (in milliseconds) to perform a base search against an LDAP server.
This metric indicates the time it took (in milliseconds) to perform a compare operation against an LDAP server. This operation simulates logging in LDAP activity.
This metric indicates the time it took (in milliseconds) to open an LDAP connection.
This metric indicates the time it took (in milliseconds) to perform an e-mail message search against an LDAP server.
The following table lists the NNTP Response metrics and their descriptions.
This metric indicates the time it took (in milliseconds) to open an NNTP connection.
This metric provides the current status of the NNTP service, either Up, Down, Status Pending, or Agent Unreachable.
This metric provides a detailed description of the status of the NNTP service when the service status is down.
This metric indicates the time it took (in milliseconds) to post a message to the news group through the NNTP service.
This metric is a container for a set of metrics you can use to measure the performance of your Oracle Application Testing Suite (OATS) transaction service test and its associated steps.
This metric indicates the overall time spent to process the OATS transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, Body Download Time, Forms Total Time, and DNS Lookup Time. The metric calculates total transaction time by assuming all the contents of a page are fetched in a serial manner.
This metric displays the total time spent in the transaction connecting to the server.
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.
This metric measures the time taken to load the contents of the page from the server.
This metric measures the total time taken to perform certain Forms operations such as Commit, Query, Runform and others.
This metric measures the time taken by the Forms operation on the server.
This metric is container for a set of metrics you can use to measure the performance of your OATS transaction service test.
This metric indicates the overall time spent to process the OATS transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, Body Download Time, Forms Total Time, and DNS Lookup Time. The metric calculates the total transaction time by assuming all the contents of a page are fetched in a serial manner.
This metric displays the total time spent in the transaction connecting to the server.
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.
This metric measures the time taken to load the contents of the page from the server.
This metric measures the total time taken to perform certain Forms operations such as Commit, Query, Runform and others.
This metric measures the time taken by the Forms operation on the server.
This metric is container for a set of metrics you can use to measure the performance of an associated step of your OATS transaction service test.
This metric indicates the overall time spent to process the OATS transaction. This includes all the phases of the transaction, including Connect Time, Redirect Time, Body Download Time, Forms Total Time, and DNS Lookup Time. The metric calculates total transaction time by assuming all the contents of a page are fetched in a serial manner.
This metric is the total time spent in the transaction connecting to the server.
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.
This metric measures the time taken to load the contents of the page from the server.
This metric measures the total time taken to perform certain Forms operations such as Commit, Query, Runform and others.
This metric measures the time taken by the Forms operation on the server.
This metric is a container for a set of metrics you can use to measure the performance of the custom script.
This metric indicates the total number of retries before the script is successfully executed.
This metric indicates the status of the service test. The test is successful of the return code of the script is 0.
This metric indicates the total time required to run the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the first line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the second line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the third line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the fourth line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the fifth line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the sixth line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the seventh line generated by the script.
A numeric value should be generated for each line of the custom script. This column corresponds to the eighth line generated by the script.
This metric is a container for a set of metrics you can use to measure the performance of the POP service test.
This metric indicates the time it took (in milliseconds) to open a POP connection.
This metric indicates the time it took (in milliseconds) to log into the POP service.
This metric displays the current status of the POP service, either Up, Down, Status Pending, or Agent Unreachable.
This metric provides a detailed description of the status of the POP service when the service status is down.
The following sections list the Port Checker metrics, their descriptions, and user actions.
This metric indicates whether agent could successfully connect to the Expected Open Ports or it could not connect to the Expected Closed Ports.
This metric is a container for a set of metrics you can use to measure the performance of the SMTP service test.
This metric indicates the time it took (in milliseconds) to open an SMTP connection.
This metric is the time it took (in milliseconds) to deliver the email. This includes the time at which the email was initiated by the sender till the time it was delivered to the receiver's email account.
This metric displays the current status of the SMTP service, either Up, Down, Status Pending, or Agent Unreachable.
This metric displays a detailed description of the status of the SMTP service when the service status is down.
The following sections list the SOAP Response metrics and their descriptions.
The following sections list the SQL Response metrics, their descriptions, and user actions.
This metric indicates the time taken to close the connection.
Close Time might be slow if the network performance is slow. Examine your network configuration.
This metric indicates the total time taken to connect to the database.
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.
This metric indicates the time taken to execute the SQL statement.
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.
This metric indicates the time taken to retrieve data from the server.
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.
This metric indicates the 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.
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.
This metric indicates the total number of rows fetched during a query.
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.
This metric indicates the time taken to prepare the SQL statement. This usually includes fetching metadata for the object types in the query.
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.
This metric indicates whether the SQL or PL/SQL statement could be successfully executed.
This metric indicates 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.
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.
This metric indicates the 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.
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.
The following sections list the TNS Ping Response metrics, their descriptions, and user actions.
This metric for a listener shows response time in milliseconds. It is calculated using the tnsping "<address>"utility. For example:
tnsping "( ADDRESS= ( PROTOCOL=TCP ) ( HOST=myhost.us.example.com ) ( PORT=15045 ) )" TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 09-SEP-2011 06:43:16 Copyright (c) 1997, 2010, Oracle. All rights reserved. Attempting to contact ( ADDRESS= ( PROTOCOL=TCP ) ( HOST=myhost.us.example.com ) ( PORT=15045 ) ) OK (2 msec)
This metric indicates the percentage of pings that did not receive a response.
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
The following sections lists the WebDAV response metrics and their descriptions.
This metric indicates whether the transaction done through the WebDAV service was successful.
This metric indicates the total time taken for the transaction made through the WebDAV service to complete.
This metric displays the total time taken to connect to the WebDAV service.
This metric displays the time taken to create a collection of files.
This metric indicates the time taken to list all the contents present in the server.
This metric indicates the time taken to create a new file through WebDAV protocol.
This metric indicates the time taken to read an existing file through WebDAV protocol.
This metric indicates the time taken to restrict the edit access to a file through WebDAV protocol.
This metric indicates the time taken to release the locked edit access to a file through WebDAV protocol.
This metric indicates the time taken to move a file from one collection to another through WebDAV protocol.
This metric is a container for a set of metrics you can use to measure the performance of your web transaction.
This metric indicates whether the web transaction was successful.
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 metric indicates 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.
This metric is container for a set of metrics you can use to measure the performance of your web transaction service test and its associated steps and steps groups.
This metric indicates whether the metric is collected for step, step group or transaction.
This metric indicates whether the web transaction was successful.
If the beacon is unable to run the step, step group, or transaction successfully, this metric returns a description of the error.
This metric 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.
This metric is a container for a set of metrics you can use to measure the performance each step in the transaction.
This metric indicates whether the web transaction was successful.
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 metric indicates 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.
This metric is container for a set of metrics you can use to measure the performance of all the steps in the step group.
This metric indicates whether the web transaction was successful.
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.
This metric indicates 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.
The following sections list the XMPP response metrics and their descriptions.
This metric indicates indicates whether the connection to the XMPP server was successful.
This metric indicates the total time taken to establish a connection to the XMPP server and list the contacts. Total time consists of Connect time, login time and contacts listing time.
This metric indicates the time taken to verify the user credentials in the XMPP server.
This metric indicates the time taken to show all the contacts for the logged in user.