| 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 Recording Service. There are two basic scenarios in which the Recording Service is used. In the first instance, a call comes in and the callee does not pick up the call. The call is forwarded to the voice mail system, where the Recording Service retrieves the callees information from the Oracle Internet Directory and verifies that the callee has voice mail access. Then the Recording Service plays the callee's greeting, records the caller's message and sends it. In the second instance, a voice mail user accesses the voice mail system and after being authenticated by the voice mail system chooses to send a message to another voice mail user, reply to the sender of the voice mail message, or forward the voice mail message to one or more recipients.
This category includes a set of metrics that provides information about the greeting response times of each individual service instance of the Recording Service.
The greeting response time for a call is the time it takes for the caller to hear the voice mail greeting once the caller has successfully logged in. Each instance can service one or more calls.
The number of calls with a specific range of greeting response times collected for each instance is labelled as Calls with < range of response times > ms. Greeting Response Time, where < range of response times > can range from 0 to 10000 milliseconds (ms), in increments of 500 ms.
The average, minimum, and maximum greeting response times, as well as the number of calls engaging in greeting activity for each instance, are also reported.
Active Recording Calls is the total number of calls playing a greeting. This total is calculated for 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 93-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 Greeting calls 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, return to the Recording Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
Average Greeting Response Time is the average greeting response time for this instance, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Average OVF Greeting 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 Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by this Recording Service instance, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources is affecting the components, review the resource usage of the Recording Service and its dependent components.
Host name of system where recording 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 Greeting Response Time is the longest greeting response time for this instance, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Maximum OVF Greeting 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 Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by this Recording Service instance, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources is affecting components, review the resource usage of the Recording 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 |
Minimum Greeting Response Time is the shortest greeting response time for this instance, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Minimum OVF Greeting 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 Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by this Recording Service instance, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources affecting the components, review the resource usage of the Recording Service and its dependent components.
This metric reports the number of calls with 0-500 milliseconds greeting 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 93-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 |
Calls with 0-500 ms Greeting 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.
This metric reports the number of calls with 1001-1500 milliseconds greeting 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 93-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 |
Calls with 1001-1500 ms Greeting 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.
This metric reports the number of calls with 1501-2000 milliseconds greeting 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 93-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 |
Calls with 1501-2000 ms Greeting 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.
This metric reports the number of calls with 2001-2500 milliseconds greeting 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 93-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 |
Calls with 2001-2500 ms Greeting 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.
This metric reports the number of calls with 2501-3000 milliseconds greeting 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 93-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 |
Calls with 2501-3000 ms Greeting 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.
This metric reports the number of calls with 3001-3500 milliseconds greeting 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 93-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 |
Calls with 3001-3500 ms Greeting 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.
This metric reports the number of calls with 3501-4000 milliseconds greeting 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 93-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 |
Calls with 3501-4000 ms Greeting 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.
This metric reports the number of calls with 4001-4500 milliseconds greeting 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 93-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 |
Calls with 4001-4500 ms Greeting 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.
This metric reports the number of calls with 4501-5000 milliseconds greeting 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 93-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 4501-5000 ms Greeting 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.
This metric reports the number of calls with 5001-5500 milliseconds greeting 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 93-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 5001-5500 ms Greeting 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.
This metric reports the number of calls with 501-1000 milliseconds greeting 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 93-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 501-1000 ms Greeting 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.
This metric reports the number of calls with 5501-6000 milliseconds greeting 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 93-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 5501-6000 ms Greeting 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.
This metric reports the number of calls with 6001-6500 milliseconds greeting 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 93-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 6001-6500 ms Greeting 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.
This metric reports the number of calls with 6501-7000 milliseconds greeting 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 93-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 6501-7000 ms Greeting 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.
This metric reports the number of calls with 7001-7500 milliseconds greeting 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 93-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 7001-7500 ms Greeting 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.
This metric reports the number of calls with 7501-8000 milliseconds greeting 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 93-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 7501-8000 ms Greeting 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.
This metric reports the number of calls with 8001-8500 milliseconds greeting 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 93-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 8001-8500 ms Greeting 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.
This metric reports the number of calls with 8501-9000 milliseconds greeting 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 93-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 8501-9000 ms Greeting 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.
This metric reports the number of calls with 9001-9500 milliseconds greeting 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 93-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 9001-9500 ms Greeting 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.
This metric reports the number of calls with 9501-10000 milliseconds greeting 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 93-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 9501-10000 ms Greeting 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.
This metric reports the number of calls with over 10000 milliseconds greeting 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 93-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 greater than 10000 ms Greeting 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.
This category contains a set of related metrics that provide you with information about the CPU and Memory being used by the Recording Service instance. Its provides a snapshot of how the Recording Service instance is performing. If a particular metric is empty, a Recording Service instance is likely down and unavailable. Check the Up/Down status metric for all the Recording Service instances.
This metric represents the percentage of the host CPU recorded for this instance of the Recording Service. By default, a critical and warning threshold value is set for this metric. Alerts will be 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 93-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 |
> |
70 |
75 |
2 |
CPU utilization of Recording 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 Recording Service instance is using the most CPU on your system, thereby leading to high end-user response times. If the instance is consuming a large amount of CPU, consider changing the configuration settings to reduce the amount of CPU consumption. To investigate why the instance is consuming a large amount of CPU, check for alerts that may have been generated by the Recording Service instance, or by the Voicemail and Fax Application that this Recording Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by 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 Recording Service 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 93-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 |
> |
80 |
90 |
2 |
Memory utilization of Recording 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 Recording Service instance is using the most memory on your system, thereby leading to high end-user response times.If the instance is consuming a large amount of memory, consider changing the configuration settings to reduce the amount of memory consumption. To investigate why the instance is consuming a large amount of memory, check for alerts that may have been generated by the Recording Service instance, or by the Voicemail and Fax Application that this Recording Service instance is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the host computer.
This metric represents the memory usage (in megabytes) for the Recording 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 Recording 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 Recording Service instance. This metric alerts you when the instance is down. If the status for an instance is down, it could mean that the instance may be in the process of starting up, or it is not responding to process management heartbeat checks. By default, a critical and warning threshold value is set for this metric. Alerts will be 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 93-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 |
0 |
1 |
Recording 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 Recording Service by selecting the Recording Service target and clicking Restart 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 Recording Service instance, or by the Voicemail and Fax Application that this Recording Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the central agent on the host computer or by the host computer.
This metric reports the number of calls with greeting response times that fall within specified intervals, for example, the number of calls with a greeting 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 greeting 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 93-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 Greeting Response Time range (ms) exceeded. |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Greeting Response Time (ms)" object.
If warning or critical threshold values are currently set for any "Greeting 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 "Greeting Response Time (ms)" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This category includes a set of metrics that provides summary information about the greeting response times of all service instances of the Recording Service. The greeting response time for a call is the time it takes for the caller to hear the voice mail greeting once the caller has successfully logged in. Each instance can service one or more calls. The average, minimum, and maximum greeting response times, as well as the number of calls engaging in greeting activity for all instances, are also reported.
Active Recording Calls is the total number of calls playing a greeting. 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 93-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 |
Active Greeting calls exceeded. |
User Action
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Recording Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
Average Greeting Response Time is the average greeting response time for all instances, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Average OVF Greeting Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by the Recording Service or by specific instances of the Recording Service, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources is affecting the components, review the resource usage of the Recording Service and its dependent components.
Maximum Greeting Response Time is the longest greeting response time across all instances, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Average OVF Maximum Greeting Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by the Recording Service or by specific instances of the Recording Service, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources is affecting components, review the resource usage of the Recording Service and its dependent components.
Minimum Greeting Response Time is the shortest greeting response time across all instances, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
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 93-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 |
Average OVF Minimum Greeting Response Time exceeded. |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Recording Service instances, outage of one or more key components in the instances, contention of common resources (for instance, Oracle Internet Directory) among Recording Service instances, resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by the Recording Service or by specific instances of the Recording Service, the Routing Service, the Voicemail & Fax Application that this Recording 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.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording 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 pages of those components to view their Up/Down status. If you suspect contention for resources is affecting the components, review the resource usage of the Recording Service and its dependent components.
This category contains a set of related metrics that provide you with information about the CPU and Memory being used by the Recording Service. Its provides a snapshot of how the Recording Service instances are performing. If a particular metric is empty, a Recording Service instance is likely down and unavailable. Check the Up/Down status metric for all the Recording Service instances.
This metric represents the percentage of the host CPU recorded for all the instances of the Recording service.
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 93-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 |
> |
70 |
75 |
2 |
CPU Utilization of Recording Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the Recording Service is using the most CPU on your system, thereby leading to high end-user response times. If the Recording Service is consuming a large amount of CPU, consider changing the configuration settings to reduce the amount of CPU consumption. To investigate why the service is consuming a large amount of CPU, check for alerts that may have been generated by specific instances of the Recording Service, or by the Voicemail and Fax Application that this Recording Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the host computer.
This metric shows you the percentage of host memory being used by the Recording Service.
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 93-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 |
> |
80 |
90 |
2 |
Memory Utilization of Recording Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the Recording Service is using the most memory on your system, thereby leading to high end-user response times. If the Recording Service is consuming a large amount of memory, consider changing the configuration settings to reduce the amount of memory consumption. To investigate why the Recording Service is consuming a large amount of memory, check for alerts that may have been generated by the Recording Service instances, or by the Voicemail and Fax Application that this Recording Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the host computer.
This metric represents the memory usage (in megabytes) for the Recording 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 Recording 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 provides information about the Up/Down status of the Recording Service. It alerts you when the Recording Service is down. The Recording Service is considered down when all of the 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 Recording Service by selecting the Recording Service target and clicking Restart 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 Recording Service or by specific instances of the Recording Service, or by the Voicemail and Fax Application that this Recording Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the central agent on the host computer or by the host computer.
This category contains metrics that provide information about the Up/Down status of the Recording Service.
This metric provides information about the Up/Down status of the Recording Service. It alerts you when the Recording Service is down. The Recording Service is considered down when all of the configured instances for this service are down.
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 93-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 |
0 |
1 |
Recording Service, %target%, is down |
User Action
You can restart the Recording Service by selecting the Recording Service target and clicking Restart 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 Recording Service or by specific instances of the Recording Service, or by the Voicemail and Fax Application that this Recording Service is a member of (check the status of dependent components - Oracle Internet Directory, Telephony Server), or by the central agent on the host computer or by the host computer.
