91 OVF Mailstore

91.1 Activity Time

This is the key column. The key is the type of activity. Examples of activity types are login time, play message time, user password.

91.1.1 Activity User Count

Number of users who performed that activity in the last five minutes.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 5 Minutes

91.1.2 Average Response Time

Sum of response time divided by number of users.

Metric Summary

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 91-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%

Multiple Thresholds

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 Editing Thresholds for information on accessing the Edit Thresholds page.

91.1.3 Sum of Response Time

Total response time for all the users for a particular activity for the last five minutes.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 5 Minutes

91.2 Database Login Time

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.

91.2.1 DB Login Time User Count

Number of users for each interval.

Metric Summary

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 91-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

Multiple Thresholds

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 Editing Thresholds for information on accessing the Edit Thresholds page.

91.3 Delivery Time

Provides a measurement of the mail delivery times.

91.3.1 Elapsed Time (msec)

Provides a measurement of the mail delivery times.

Metric Summary

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 91-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%

91.4 Listen To Message Time

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.

91.4.1 Listen Time User Count

Number of users for each interval.

Metric Summary

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 91-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

Multiple Thresholds

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 Editing Thresholds for information on accessing the Edit Thresholds page.

91.5 Response

Provides the status of the backend mailstore database.

91.5.1 Status

Provides the status of the backend mailstore database.

Metric Summary

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 91-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

91.6 User Login Time

Divides the login time into intervals. For example, 0-100ms, 100-200ms, 200 - 300ms. Gives the number of users whose login time fits into each interval. For example, 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.

91.6.1 User Count for Login Time

Displays the number of users for each interval.

Metric Summary

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 91-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

Multiple Thresholds

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 Editing Thresholds for information on accessing the Edit Thresholds page.