The document introduces Oracle Application Testing Suite's e-Load and ServerStats tools. ServerStats can monitor performance across application tiers in real-time with charts and alarms. It saves data to e-Reporter to correlate with load test results from e-Load for bottleneck analysis. Key server metrics discussed include CPU usage, memory usage, hits/requests per second, queue times, and disk and database activity. The document provides instructions for configuring new ServerStats monitors and metrics profiles to collect specific performance data from web servers, application servers, and database servers during load tests.

1. ServerStats Introduction to Oracle Application Testing Suite: e-Load

2. ServerStats Server performance monitoring tool Collects data from various tiers Real-time displays Charting capabilities and alarm setup Server data saved to e-Reporter Correlated with load test results from e-Load for bottleneck analysis Add new ServerStats monitors to a running load test session. A URL Data Source is available for collecting performance metrics that are accessible via a Web page (that is, Apache performance statistics). The Metrics interface allows you to enable multiple metrics to be created at once.

3. Back-End System Monitoring System Architecture Map

4. What Systems to Monitor Look at a system architecture map, determine what systems are contained within the web application. Talk to developers or system architects to learn about the various pieces of the system and how they interact. Also, determine who will monitor and setup these counters. Individuals responsible for monitoring might be a system admin, DBA or QA engineer for example.

5. Useful Counters on Web Server CPU Usage Memory Usage Hits/pages per second Web process system utilization Current connections Disk swapping Disk utilization

6. Useful Counters on Application Servers CPU Usage Memory Usage Hits/pages per second Request queue Application Server process system utilization Queue wait time Disk swapping Disk utilization

7. Useful Counters on Database Servers CPU Usage Memory Usage Database process system utilization Table scans Query wait times Selects/inserts/deletes/updates per second SQL recompilations Table locks Index hits (%)

8. Run-Time ServerStats Configuration ServerStats configuration is located under the “Set up autopilot” tab To Create new or edit existing ServerStats Monitors click “Edit Configurations” or select from the ServerStats menu.

9. Add New ServerStats Configuration ServerStats > Configurations

10. ServerStats Configurations Click the “New” button to add a new configuration Use the Edit button to modify an existing configuration Use the Delete button to delete and existing configuration Click the “New” button under monitors after you create a configuration

11. Add New Monitor Click on “Add a New Monitor” Select monitor to add Data Sources Metrics Metric Profiles

12. Configure Data Sources

13. Configure Data Sources Click edit and enter a user who has appropriate access to the system.

14. Configure Data Sources Click next to discover. Select the desired monitor as shown. In this example, we choose memory and CPU objects.

15. Configure Data Sources After clicking finish, the following screen is shown

16. Metrics The process for configuring a metric (individual monitor) is the similar to that of the data source. Metric is done one by one and automatically selects an appropriate data source.

17. Metric Profiles Metric Profiles are used to configure several monitors in one step. Commonly used metrics are preconfigured in the profiles Data sources are automatically selected when creating metric profiles.

18. Select ServerStats Configuration Before starting a test, select the appropriate ServerStats configuration to use. Monitors for that configuration will be displayed in the monitors window

19. Exercise 3 Set up server stats to collect the following information. If possible, set this up to monitor the web server, otherwise just setup to monitor the e-Load client machine executing the VU’s Percent CPU and Percent Memory Utilization Web Server Total Requests/Sec (if available) Application Server Queued Requests (if available) Database Server User Connections (if available) Rerun the load test that you setup in Workshop 1 but this time collect the ServerStats data