Use this page to define an usage metric for the service based on the underlying system components.
Select the Target Type from the drop down list and then select the metric. This metric will be used as the basis for monitoring usage of the service. For example, if you are defining an email service, which depends on an IMAP server, then you can use the ‘Total Client Connections' metric of the IMAP server to represent usage of this email service.
You can choose the value of the metric from a specific component or from multiple components. If multiple components are chosen, choose the aggregation function.
Maximum: The maximum value of the metric across all components will be used as the value of this usage metric for the service.
Minimum: The minimum value of the metric across all components will be used as the value of this usage metric for the service.
Average: The average value of the metric across all components will be used.
Sum: The sum of the values of metrics across all components will be calculated.
Some metrics might have associated key values, where you can further quality the object that is being monitored For example, the Filesystem Space Available(%) metric could be qualified by the name of a particular mount point.
Related Topics
About ServicesEnterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.