Use this page to define the metrics that will be used to measure the performance of your service. If a service test has been defined for this service, then the response time measurements as a result of executing that service test can be used as a basis for the service's performance metrics. Alternatively, metrics from the underlying system components can also be used to measure performance of a service.
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 dropdown 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.
Delete a metric from the list. Select a metric and click Remove.
If a service test has been defined to monitor the availability of your service,add a performance metric based on service test.
Choose the metric that best represents the overall performance of the service as the chart to be displayed on the Service Home page.
If you delete a metric, the performance metrics of the aggregate / generic services dependent on this metric will be impacted.
Note: If 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
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.