|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
Provides the status of the backend mailstore database.
This is the key column. The key is the type of activity. Examples of activity types are login time, play message time, user password.
Number of users who performed that activity in the last five minutes.
Sum of response time divided by number of user.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-1 Metric Summary Table
| Target Version | Key | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|---|
| All Versions | activity_name: "PLAY_MSG" | Every 5 Minutes | After Every Sample | > | 2000 | 2500 | 1 | The vm average play message time is %value% |
For this metric you can set different warning and critical threshold values for each "Voicemail Activity" object.
If warning or critical threshold values are currently set for any "Voicemail Activity" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Voicemail Activity" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager onling help for information on accessing the Edit Thresholds page.
Divides the amount of time it takes to login to database into intervals. Gives the number of users whose database login times fits into each interval.
Number of users for each interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-2 Metric Summary Table
| Target Version | Key | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|---|
| All Versions | response_duration: ">2000" | Every 5 Minutes | After Every Sample | > | 1 | 5 | 1 | The DB login time is greater than 2000 for %value% users |
For this metric you can set different warning and critical threshold values for each "Response Duration (msec)" object.
If warning or critical threshold values are currently set for any "Response Duration (msec)" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Response Duration (msec)" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager onling help for information on accessing the Edit Thresholds page.
Provides a measurement of the mail delivery times.
Provides a measurement of the mail delivery times.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-3 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | > | 300000 | 600000 | 1 | The voicemail delivery time is %value% |
Divides the amount of time it takes to listen to messages into intervals. Gives the number of users whose listen times fits into each interval.
Number of users for each interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-4 Metric Summary Table
| Target Version | Key | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|---|
| All Versions | response_duration: ">10000" | Every 5 Minutes | After Every Sample | > | 1 | 5 | 1 | The play message time is greater than 10000 for %value% users |
For this metric you can set different warning and critical threshold values for each "Response Duration (msec)" object.
If warning or critical threshold values are currently set for any "Response Duration (msec)" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Response Duration (msec)" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager onling help for information on accessing the Edit Thresholds page.
Provides the status of the backend mailstore database.
Provides the status of the backend mailstore database.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-5 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
| All Versions | Every 5 Minutes | After Every Sample | =
|
Not Defined | 0 | 1 | Failed to connect to the database |
Divides the login time into intervals. Eg, 0-100ms, 100-200ms,200 - 300ms. Gives the number of users whose login time fits into each interval. Eg, It took 8 users 0-100ms to login, 3 users 100-200ms, and 1 user 200-300ms. This type of metric is common in OVF and repeated several times below.
Displays the number of users for each interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 27-6 Metric Summary Table
| Target Version | Key | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|---|
| All Versions | response_duration: ">10000" | Every 5 Minutes | After Every Sample | > | 1 | 5 | 1 | The response duration is > 10000 for %value% users |
For this metric you can set different warning and critical threshold values for each "Response Duration (msec)" object.
If warning or critical threshold values are currently set for any "Response Duration (msec)" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Response Duration (msec)" object, use the Edit Thresholds page. See the Editing Thresholds topic in the Enterprise Manager onling help for information on accessing the Edit Thresholds page.
