Create / Edit Service Test - HTTP Ping Page

URL

Specify the URL of the Web site that you wish to monitor.

Request Method

If you select HEAD here, only the HTTP headers are retrieved. This reduces the network traffic.

Accept-Language Header

Specify the language header like 'en' for English.

You can specify additional headers if required. These headers need to be in the form -header1:value1#header2 :value2

Status

Indicates whether the HTML request was successful.

User Action
Use the total transaction time metric to identify problem pages. After you identify a page or transaction that's slow to response 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. 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 indicate that there may be too many connections made during the transaction. Consider enabling HTTP persistent connections if the application does not already have them enabled.

User Action
Significant time taken to redirect the HTTP request suggests that there are too many redirects in the application or that the redirecting server is slow. If the redirect is causing the performance problems, consider alternative solutions to sending the user to another HTML page.

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 a high network latency between the agent and the service. Some applications generate an entire page before sending the first byte of that page. For such applications, a high First Byte Time could also indicate that the servers are taking a long time to generate each page.

Enterprise Manager breaks down each transaction into individual phases. Performance metrics for each phase of the transaction can help you pinpoint the cause of a slow response time alert. This metric measures the HTML Time, which is the amount of time it takes to transfer the HTML coding of the page to the browser. This metric does not include the time spent transferring images or other page content.

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.

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.

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.