Use this page to define the metrics that will be used to measure the performance of your Web application. If a service test has been defined for this Web application, then the response time measurements as a result of executing that service test can be used as a basis for the Web application's performance metrics. Alternatively, performance metrics from the underlying system components can also be used to determine the performance of a Web application.
Performance metrics to help you identify how well the service test is performing for each of the remote beacons. In general, the local beacon should have a very efficient and consistent response time because it is local to the Web application host. Remote beacons provide data to reflect the response time experienced by your application end users.
You can:
Add a performance metric. Select a value from the drop down list and click Go. If you select Based on Service Test, the Performance Metrics: Add Performance Metric based on Service Test page is displayed. If you select Based on System, the Performance Metrics: Add Performance Metric based on System page is displayed.
Note: You cannot change the name of the metrics. The metric names should be unique.
Choose to create a performance metric based on service test; if a service test has been defined to monitor availability of your service.
Note: When you are creating a Web application, depending on the test type, a few performance metrics are added by default. For example, HTTP Transaction - Perceived Total Time (ms) is created when a Web transaction is created.
Related Topics
About Web Application Management
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.