| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
View PDF |
| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
View PDF |
This target represents the Retrieval Service. The Retrieval Service allows users to listen to, save, delete, reply to, and forward voice mail messages, set passwords, leave a voice mail for another user, and record and activate greetings. The Retrieval Service formulates the mail box number using the caller ID or prompts the voice mail user to enter a mail box number. The Retrieval Service verifies that the user is a valid voice mail user against the data stored in the Oracle Internet Directory. Once the user has been verified, the user is prompted for a password, and the voice mail system authenticates the password against the Oracle Internet Directory. Upon successful authentication, the Retrieval Service interacts with the Collaboration Suite Database to retrieve voice mail messages and other account information. A user who cannot be validated has the option to transfer to another users voice mail box by pressing the asterisk symbol during or after the prompt to enter the mail box number is played.
This category includes a set of metrics that provides summary information about the login response time, menu play time, and message play time for this instance of the Retrieval Service.
The login response time for a call is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
The menu play time is the length of time, in milliseconds, it takes to play the Message Menu after the message count is played.
The message play time is the length of time, in milliseconds, between the time the user chooses to hear the message and when the message starts playing.
Each retrieval instance can service one or more calls.
The login response time metrics are called Calls with < range of response times > ms. Login Response Time, and the message play time metrics are called Calls with < range of response times > ms. Message Play Time, where < range of response times > can range from 0 to 10000 milliseconds (ms), in increments of 500 milliseconds. For menu play time, the range is from 0 to 2000 milliseconds, in increments of 100 milliseconds.
The average, minimum, and maximum response times, as well as the number of calls engaging in the activity for this instance, are also reported.
Active Logins is the total number of calls where the user is in the process of logging in and is waiting to hear the message count. This total is calculated for all calls serviced by this instance, over the time period specified in the View Data field.
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 94-1 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 |
Not Defined |
1 |
Active OVF Logins exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Active Menu Play Calls is the total number of calls where the message count has been played, and the user is waiting to hear the Message Menu. This total is calculated for all calls serviced by this instance, over the time period specified in the View Data field.
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 94-2 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 |
Not Defined |
1 |
Active Message Menu actions exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Active Message Play Calls is the total number of calls where the user has chosen to hear the message and is waiting for the message to start playing. This total is calculated for this instance, over the time period specified in the View Data field.
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 94-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 |
> |
Not Defined |
Not Defined |
1 |
Active Message Play actions exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Average Login Response Time is the average login response time for this instance, over the time period specified in the View Data field. Login response time is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-4 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 |
Not Defined |
1 |
Average OVF Login Response Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Menu Play Time is the average length of time this instance takes to play the Message Menu after the message count is played, over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-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 |
Not Defined |
1 |
OVF Menu Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Message Play Time is the average message play time for this instance, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and when the message starts playing. The time is measured in milliseconds.
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 94-6 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 |
Not Defined |
1 |
Average OVF Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Host name of system where retrieval instance is running.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Maximum Login Response Time is the longest login response time for this instance, over the time period specified in the View Data field. Login response time for a call is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-7 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 |
Not Defined |
1 |
Maximum OVF Login Response Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Maximum Menu Play Time is the longest time this instance takes to play the Message Menu after the message count is played over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-8 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 |
Not Defined |
1 |
Maximum OVF Menu Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Maximum Message Play Time is the longest message play time for this instance, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and the message starts playing. The time is measured in milliseconds.
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 94-9 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 |
Not Defined |
1 |
Maximum OVF Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the large average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Login Response Time is the shortest login response time for this instance, over the time period specified in the View Data field. Login response time for a call is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-10 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 |
Not Defined |
1 |
Minimum OVF Login Response Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Menu Play Time is the shortest time this instance takes to play the Message Menu after the message count is played over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-11 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 |
Not Defined |
1 |
Minimum OVF Menu Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Message Play Time is the shortest message play time for this instance, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and the message starts playing. The time is measured in milliseconds.
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 94-12 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 |
Not Defined |
1 |
Minimum OVF Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by this instance of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contentionis affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Name of the metric.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric reports the number of calls with 0-100 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-13 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 |
Not Defined |
1 |
Calls with 0-100 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 0-500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-14 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 |
Not Defined |
1 |
Calls with 0-500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 0-500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-15 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 |
Not Defined |
1 |
Calls with 0-500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1001-1100 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-16 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 |
Not Defined |
1 |
Calls with 1001-1100 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1001-1500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-17 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 |
Not Defined |
1 |
Calls with 1001-1500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1001-1500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-18 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 |
Not Defined |
1 |
Calls with 1001-1500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 101-200 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-19 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 |
Not Defined |
1 |
Calls with 101-200 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1101-1200 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-20 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 |
Not Defined |
1 |
Calls with 1101-1200 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1201-1300 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-21 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 |
Not Defined |
1 |
Calls with 1201-1300 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1301-1400 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-22 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 |
Not Defined |
1 |
Calls with 1301-1400 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1401-1500 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-23 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 |
Not Defined |
1 |
Calls with 1401-1500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1501-1600 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-24 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 |
Not Defined |
1 |
Calls with 1501-1600 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1501-2000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-25 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 |
Not Defined |
1 |
Calls with 1501-2000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1501-2000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-26 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 |
Not Defined |
1 |
Calls with 1501-2000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1601-1700 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-27 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 |
Not Defined |
1 |
Calls with 1601-1700 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1701-1800 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-28 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 |
Not Defined |
1 |
Calls with 1701-1800 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1801-1900 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-29 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 |
Not Defined |
1 |
Calls with 1801-1900 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 1901-2000 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-30 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 |
Not Defined |
1 |
Calls with 1901-2000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 2001-2500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-31 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 |
Not Defined |
1 |
Calls with 2001-2500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 2001-2500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-32 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 |
Not Defined |
1 |
Calls with 2001-2500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 201-300 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-33 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 |
Not Defined |
1 |
Calls with 201-300 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 2501-3000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-34 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 |
Not Defined |
1 |
Calls with 2501-3000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 2501-3000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-35 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 |
Not Defined |
1 |
Calls with 2501-3000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 3001-3500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-36 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 |
Not Defined |
1 |
Calls with 3001-3500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 3001-3500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-37 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 |
Not Defined |
1 |
Calls with 3001-3500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 301-400 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-38 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 |
Not Defined |
1 |
Calls with 301-400 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 3501-4000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-39 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 |
Not Defined |
1 |
Calls with 3501-4000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 3501-4000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-40 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 |
Not Defined |
1 |
Calls with 3501-4000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 4001-4500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-41 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 |
Not Defined |
1 |
Calls with 4001-4500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 4001-4500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-42 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 |
Not Defined |
1 |
Calls with 4001-4500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 401-500 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-43 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 |
Not Defined |
1 |
Calls with 401-500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 4501-5000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-44 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 |
Not Defined |
1 |
Calls with 4501-5000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 4501-5000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-45 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 |
Not Defined |
1 |
Calls with 4501-5000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 5001-5500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-46 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 |
Not Defined |
1 |
Calls with 5001-5500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 5001-5500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-47 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 |
Not Defined |
1 |
Calls with 5001-5500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 501-1000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-48 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 |
Not Defined |
1 |
Calls with 501-1000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 501-1000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-49 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 |
Not Defined |
1 |
Calls with 501-1000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 501-600 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-50 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 |
Not Defined |
1 |
Calls with 501-600 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 5501-6000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-51 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 |
Not Defined |
1 |
Calls with 5501-6000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 5501-6000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-52 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 |
Not Defined |
1 |
Calls with 5501-6000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 6001-6500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-53 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 |
Not Defined |
1 |
Calls with 6001-6500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 6001-6500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-54 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 |
Not Defined |
1 |
Calls with 6001-6500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 601-700 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-55 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 |
Not Defined |
1 |
Calls with 601-700 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 6501-7000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-56 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 |
Not Defined |
1 |
Calls with 6501-7000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 6501-7000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-57 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 |
Not Defined |
1 |
Calls with 6501-7000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 7001-7500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-58 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 |
Not Defined |
1 |
Calls with 7001-7500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 7001-7500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-59 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 |
Not Defined |
1 |
Calls with 7001-7500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 701-800 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-60 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 |
Not Defined |
1 |
Calls with 701-800 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 7501-8000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-61 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 |
Not Defined |
1 |
Calls with 7501-8000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 7501-8000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-62 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 |
Not Defined |
1 |
Calls with 7501-8000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 8001-8500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-63 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 |
Not Defined |
1 |
Calls with 8001-8500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 8001-8500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-64 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 |
Not Defined |
1 |
Calls with 8001-8500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 801-900 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-65 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 |
Not Defined |
1 |
Calls with 801-900 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 8501-9000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-66 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 |
Not Defined |
1 |
Calls with 8501-9000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 8501-9000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-67 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 |
Not Defined |
1 |
Calls with 8501-9000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 9001-9500 milliseconds login response times, collected for all calls serviced by this instance.
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 94-68 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 |
Not Defined |
1 |
Calls with 9001-9500 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 9001-9500 milliseconds message play times, collected for all calls serviced by this instance.
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 94-69 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 |
Not Defined |
1 |
Calls with 9001-9500 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 901-1000 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-70 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 |
Not Defined |
1 |
Calls with 901-1000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 9501-10000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-71 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 |
Not Defined |
1 |
Calls with 9501-10000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with 9501-10000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-72 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 |
Not Defined |
1 |
Calls with 9501-10000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with over 10000 milliseconds login response times, collected for all calls serviced by this instance.
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 94-73 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 |
Not Defined |
1 |
Calls with greater than 10000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with over 10000 milliseconds message play times, collected for all calls serviced by this instance.
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 94-74 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 |
Not Defined |
1 |
Calls with greater than 10000 ms Message Play Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with over 2000 milliseconds menu play times, collected for all calls serviced by this instance.
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 94-75 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 |
Not Defined |
1 |
Calls with greater than 2000 ms Login Time exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Process Name" object.
If warning or critical threshold values are currently set for any "Process Name" 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 "Process Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the Retrieval Service instance. It provides a snapshot of how the Retrieval Service instance is performing. If a particular metric is empty, it is likely that the service instance is down and unavailable. Check the Up/Down status metric of the Retrieval Service instance.
This metric represents the percentage of the host CPU recorded for this instance of the Retrieval Service. By default, a critical and warning threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-76 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 |
> |
70 |
75 |
2 |
CPU utilization of Retrieval Instance, %target% (%Name%), is %value%%% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" 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 "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
You can use this metric to determine if the Retrieval Service instance is using the most CPU on your system, thereby leading to high end-user response times. If the service instance is consuming a large amount of CPU, consider changing the configuration settings to reduce the CPU consumption. To investigate the cause of the CPU consumption, check for alerts that may have been generated by the following: the Retrieval Service instance, the Voicemail and Fax Application that this Retrieval Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric shows you the percentage of host memory being used by the Retrieval Service instance. By default, a critical and warning threshold value is set for this metric column. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-77 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 |
> |
80 |
90 |
2 |
Memory utilization of Retrieval Instance, %target% (%Name%), is %value%%% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" 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 "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
You can use this metric to determine if this Retrieval Service instance is using the most memory on your system and leading to high end-user response times. If the service instance is consuming a large amount of memory, consider changing the configuration settings to reduce memory consumption. To investigate the cause of the memory consumption, check for alerts that may have been generated by the following: the Retrieval Service instance, the Voicemail and Fax Application that this Retrieval Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the Retrieval Service instance.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Retrieval Service instance.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric provides information about the Up/Down status of the Retrieval Service instance and alerts you when the Retrieval Service instance is down. If the status is down, it could mean that the service instance is in the process of starting up, or it is not responding to process management heartbeat checks. By default, a critical threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-78 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 |
Retrieval Instance, %target% (%Name%), is down |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" 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 "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
You can restart the Retrieval Service by selecting the Retrieval Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the instance is down, check for alerts that may have been generated by the following: the Retrieval Service instance, the Voicemail and Fax Application that this Retrieval Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This metric reports the number of calls with login response times that fall within specified intervals, for example, the number of calls with a login response time of 0-500 milliseconds. "Number of Calls" is the calls reported for all instances during the collection interval. See the Number of Calls metric for additional details.
This metric provides additional metrics on login response time for each specified 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 94-79 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 |
Not Defined |
1 |
Calls with Login Response Time range (ms) exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Login Response Time (ms)" object.
If warning or critical threshold values are currently set for any "Login Response Time (ms)" 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 "Login Response Time (ms)" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with menu play times that fall within specified intervals, for example, the number of calls with a menu play time of 0-100 milliseconds. "Number of Calls" is the calls reported for all instances during the collection interval. See the Number of Calls metric for additional details.
This metric provides additional information on menu play time for each specified 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 94-80 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 |
Not Defined |
1 |
Calls with Menu Play Response Time range (ms) exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Menu Play Time (ms)" object.
If warning or critical threshold values are currently set for any "Menu Play Time (ms)" 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 "Menu Play Time (ms)" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric reports the number of calls with message play times that fall within specified intervals, for example, the number of calls with a message play time of 0-500 milliseconds. "Number of Calls" is the calls reported for all instances during the collection interval. See the Number of Calls metric for additional details.
This metric provides additional metrics on menu play time for each specified 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 94-81 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 |
Not Defined |
1 |
Calls with Message Play Response Time range (ms) exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Message Play Time (ms)" object.
If warning or critical threshold values are currently set for any "Message Play Time (ms)" 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 "Message Play Time (ms)" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This category contains a set of metrics that provides summary information about the login response time, menu play time and message play time of all service instances in the Retrieval Service. The login response time for a call is the time is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count. The menu play time is the length of time, in milliseconds, it takes to play the Message Menu after the message count is played. The message play time is the length of time, in milliseconds, between the time the user chooses to hear the message and when the message starts playing. Each retrieval instance can service one or more calls. The average, minimum, and maximum response times, as well as the number of calls engaging in the activity for all instances are reported.
Active Logins is the total number of calls where the user is in the process of logging in and is waiting to hear the message count. This total is calculated for all instances over the time period specified in the View Data field.
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 94-82 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 |
Not Defined |
1 |
Active OVF Logins exceeded. |
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Active Menu Play Calls is the total number of calls where the message count has been played, and the user is waiting to hear the Message Menu. This total is calculated for all instances, over the time period specified in the View Data field.
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 94-83 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 |
Not Defined |
1 |
Active Message Menu actions exceeded. |
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Active Message Play Calls is the total number of calls where the user has chosen to hear the message and is waiting for the message to start playing. This total is calculated for all instances over the time period specified in the View Data field.
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 94-84 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 |
Not Defined |
1 |
Active Message Play actions exceeded. |
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, go to the Retrieval Service home page, and click the Add One Instance button to increase the number of service instances.
Average Login Response Time is the average login response time for all instances, over the time period specified in the View Data field. Login response time is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-85 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 |
Not Defined |
1 |
OVF Login Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Menu Play Time is the average length of time it takes to play the Message Menu after the message count is played, for all instances, over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-86 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 |
Not Defined |
1 |
OVF Menu Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Message Play Time is the message play time, averaged across all instances, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and when the message starts playing. The time is measured in milliseconds.
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 94-87 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 |
Not Defined |
1 |
OVF Message Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Maximum Login Response Time is the longest login response time across all instances, over the time period specified in the View Data field. Login response time for a call is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-88 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 |
Not Defined |
1 |
Maximum OVF Login Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Maximum Menu Play Time is the longest time it takes to play the Message Menu after the message count is played, for all instances, over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-89 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 |
Not Defined |
1 |
Maximum OVF Menu Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Maximum Message Play Time is the longest message play time for call serviced by all instances, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and the message starts playing. The time is measured in milliseconds.
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 94-90 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 |
Not Defined |
1 |
Maximum OVF Message Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Login Response Time is the shortest login response time across all instances, over the time period specified in the View Data field. Login response time for a call is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
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 94-91 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 |
Not Defined |
1 |
Minimum OVF Login Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Menu Play Time is the shortest time it takes to play the Message Menu after the message count is played, for all instances, over the time period specified in the View Data field. The time is measured in milliseconds.
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 94-92 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 |
Not Defined |
1 |
Minimum OVF Menu Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or by specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Minimum Message Play Time is the shortest message play time for calls serviced by all instances, over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and the message starts playing. The time is measured in milliseconds.
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 94-93 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 |
Not Defined |
1 |
Minimum OVF Message Play Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to the outage of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home page of the components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the Retrieval Service. It provides a snapshot of how the Retrieval Service instances are performing. If a particular metric is empty, it is likely that an Retrieval Service instance is down and unavailable. Check the Up/Down status metric for all the Retrieval Service instances.
This metric represents the percentage of the host CPU recorded for all the instances of the service. By default, a critical and warning threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-94 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 |
> |
70 |
75 |
2 |
CPU utilization of Retrieval Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the Retrieval Service is using the most CPU on your system, thereby leading to high end-user response times. If the Retrieval Service is consuming a large amount of CPU, consider changing the configuration settings to reduce the CPU consumption. To investigate the cause of the CPU consumption, check for alerts that may have been generated by the following: the specific instances of the Retrieval Service, the Voicemail and Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric shows you the percentage of host memory being used by the service. By default, a critical and warning threshold value is set for this metric column. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-95 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 |
> |
80 |
90 |
2 |
Memory utilization of Retrieval Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the Retrieval Service is using the most memory on your system and leading to high end-user response times. If the Retrieval Service is consuming a large amount of memory, consider changing the configuration settings to reduce memory consumption. To investigate the cause of the memory consumption, check for alerts that may have been generated by the following: the Retrieval Service instances, the Voicemail and Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the service.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Retrieval Service.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric provides information about the Up/Down status of the Retrieval Service. The Retrieval Service shows a status of Down when all configured instances for this service are down.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
You can restart the Retrieval Service by selecting the Retrieval Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by the following: the Retrieval Service or specific instances of the Retrieval Service, the Voicemail and Fax Application that this Retrieval Service is a member of (check for check the status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category contains metrics that provide information about the Up/Down status of the Retrieval Service.
This metric provides information about the Up/Down status of the Retrieval Service and alerts you when the Retrieval Service is down. The Retrieval Service shows a status of Down when all configured instances for this service are down. By default, a critical threshold value is set for this metric. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
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 94-96 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 |
Retrieval Service, %target%, is down |
User Action
You can restart the Retrieval Service by selecting the Retrieval Service target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by the following: the Retrieval Service or specific instances of the Retrieval Service, the Voicemail and Fax Application that this Retrieval Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
