This page shows detailed analysis reports of the page being monitored.
The request path, the sequence and site address is displayed. The most commonly used axis is the request. By analyzing a selected request, you can first display a set of metrics that summarize the overall response time of the selected request over the past 24 hours.
The results of the analysis based on the analysis path is displayed. The number of samples, response time and server time are displayed. A summary of the results is displayed followed by the detailed view. You can select filters and choose to view the details by URL, domain, region, visitor and Web server.
For each domain, the following information is displayed:
The average response time experienced by users from that domain
The number of times users from that domain accessed your Web application pages
The total time spent on your site by users from that domain
The average values are calculated based on the time period you select. The value can be 24 hours, seven days, or 31 days. As a result, you can identify whether or not specific domains are experiencing any particular performance problems when using your Web application.
Tip: You can also organize domains into regions and then filter your end user response data by each region. For more information, see Adding Regions.
For each region, Enterprise Manager displays:
The average response time experienced by users from that region
The number of times users from that region accessed your Web application pages
The total time spent on your site by users from that region
The average values are calculated based on the time period you select. The value can be 24 hours, seven days, or 31 days. As a result, you can identify whether or not specific regions are experiencing any particular performance problems when using your Web application.
For each visitor, the following information is displayed:
The average response time experienced by the user
The number of times the user has accessed your Web application pages
The total time the user has spent on your site
Note: Visitors to a Web application are not always identified by their user name. However, you can often identify a particular user by the name of the host computer or the domain name used to access the Web site. For more information, see Adding Regions.
If your Web application contains more than one Web server component, you can use this page to view charts that compare the performance of the Web server instances. Using the Hourly Average Response by Webserver chart you can easily tell if one of your Web server instances is having performance problems.
Be sure to compare the results, however, with the number of hits on the Web server instances. Ideally, if you are using a server load balancer, the number of hits and the response time for each Web server should be similar. However, if one Web server is experiencing more hits than the other, the Web server that is experiencing a heavier load will likely produce slower response times.
For more information on the analysis path and results, see About End-User Performance Analysis Reports.
Related Topics
About Web Application Management
Using the End-User Response Time Views
About Monitoring End-User Performance
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.