| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Oracle Collaboration Suite Metric Reference Manual 10g Release 2 (10.2) Part Number B25985-01 |
|
|
PDF · Mobi · ePub |
This target represents the Message Delivery Monitor Service. The Message Delivery Monitor Service measures the time it takes to send a message to the Collaboration Suite Database. It sends test messages to a test account on each Collaboration Suite Database, and reports the time it takes for the test message to arrive in the Inbox of the target Collaboration Suite Database.
This category includes a set of metrics that provides information about the message delivery times of this service instance in the Message Delivery Monitor Service.
Once a caller confirms that he or she has completed recording a message, the message is sent to the called party's mailbox, at which time the message is available for the called party's retrieval. The message delivery time for a call is the length of time, in seconds, it takes to deliver the recorded message to the target Collaboration Suite Database. Each instance can service one or more calls.
The number of calls with a specific range of message delivery times collected for this instance are labelled as Calls with < range of message delivery times > ms. Message Delivery Time, where < range of message delivery times > can range from 0 to 10000 seconds (ms), in increments of 500 ms. The number of calls with over 1000 seconds message delivery time is reported in Calls with over 10000 ms. Message Delivery Time.
The average, minimum, and maximum message delivery times, as well as the number of calls engaging in message delivery activity for this instance, are also reported.
Average Message Delivery Time is the average message delivery time for this instance, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 |
Average OVF Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the status of dependent components -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the message delivery service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service and its dependent components.
Maximum Message Delivery Time is the longest message delivery time for this instance, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 |
Maximum OVF Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or by specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the dependent component status -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service and its dependent components.
Minimum Message Delivery Time is the shortest message delivery time for this instance, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 |
Minimum OVF Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or by specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the dependent component status -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 status. If you suspect contention for resources is affecting the components, review the resource usage of the Message Delivery Monitor Service and its dependent components.
This metric reports the number of calls with 0-500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 |
Calls with 0-500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 1001-1500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 1001-1500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 1501-2000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 1501-2000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 2001-2500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 2001-2500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 2501-3000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 2501-3000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 3001-3500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 3001-3500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 3501-4000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 3501-4000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 4001-4500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 4001-4500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 4501-5000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 4501-5000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 5001-5500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 5001-5500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 501-1000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 501-1000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 5501-6000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 5501-6000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 6001-6500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 6001-6500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 6501-7000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 6501-7000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 7001-7500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 7001-7500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 7501-8000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 7501-8000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 8001-8500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 8001-8500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 8501-9000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 8501-9000 s Message Delivery Time exceeded. |
This metric reports the number of calls with 9001-9500 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 9001-9500 s Message Delivery Time exceeded. |
This metric reports the number of calls with 9501-10000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 9501-10000 s Message Delivery Time exceeded. |
This metric reports the number of calls with over 10000 seconds message delivery times, collected for all calls serviced by this instance.
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 79-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 greater than 10000 s Message Delivery Time exceeded. |
Name of the Collaboration Suite Database where the recorded message is stored. This is the Collaboration Suite Database where the message delivery test account is set up.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the Message Delivery Monitor Service instance. It provides a snapshot of how the Message Delivery Monitor 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 Message Delivery Monitor Service instance.
This metric represents the percentage of the host CPU recorded for this instance of the Message Delivery Monitor 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.
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 79-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 |
> |
70 |
75 |
2 |
CPU utilization of Message Delivery Monitor Instance, %target% (%Name%), is %value%%% |
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.
You can use this metric to determine if the Message Delivery Monitor 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 Message Delivery Monitor Service instance, the Voicemail and Fax Application that this Message Delivery Monitor 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.
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 Message Delivery Monitor 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.
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 79-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 |
> |
80 |
90 |
2 |
Memory utilization of Message Delivery Monitor Instance, %target% (%Name%), is %value%%% |
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.
You can use this metric to determine if this Message Delivery Monitor 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 Message Delivery Monitor Service instance, the Voicemail and Fax Application that this Message Delivery Monitor 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 Message Delivery Monitor Service instance.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Message Delivery Monitor Service instance.
This metric is for internal use only.
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.
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 Message Delivery Monitor Service instance and alerts you when the Message Delivery Monitor 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.
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 79-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 |
0 |
1 |
Message Delivery Monitor Instance, %target% (%Name%), is down |
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.
You can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service instance, the Voicemail and Fax Application that this Message Delivery Monitor 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 message delivery times that fall within specified intervals, for example, the number of calls with a message delivery 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 message delivery time for each specified interval.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 79-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 Message Delivery Response Time range (s) exceeded. |
For this metric you can set different warning and critical threshold values for each "Message Delivery Time (sec.)" object.
If warning or critical threshold values are currently set for any "Message Delivery Time (sec.)" 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 Delivery Time (sec.)" 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 message delivery times of all service instances in the Message Delivery Monitor Service. Once a caller confirms that he or she has completed recording a message, the message is sent to the called party's mailbox, at which time the message is available for the called party's retrieval. The message delivery time for a call is the length of time, in seconds, it takes to deliver the recorded message to the target Collaboration Suite Database. Each instance can service one or more calls. The average, minimum, and maximum message delivery times are reported.
Average Message Delivery Time is the average message delivery time for all instances, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 |
Average OVF Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or by specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the dependent component status -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service and its dependent components.
Maximum Message Delivery Time is the longest message delivery time for all instances, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 |
Average OVF Maximum Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or by specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the status of dependent components -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service and its dependent components.
Minimum Message Delivery Time is the shortest message delivery time for all instances, over the time period specified in the View Data field. Message delivery time is the time, in seconds, it takes to deliver a message to the mail box.
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 79-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 Minimum Message Delivery Time exceeded. |
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Monitor Service instances, outage of one or more key components in the instances, contention for common resourcesd (for example, Oracle Internet Directory) among Message Delivery Monitor Service instances, resource shortage among key components in the instances.
To investigate why the message delivery time exceeded the response time value set, check for alerts that may have been generated by the Message Delivery Monitor Service or by specific instances of the Message Delivery Monitor Service, the Voicemail & Fax Application that this Message Delivery Monitor Service is a member of (check the dependent component status -- Oracle Internet Directory, Collaboration Suite Databases, 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 message delivery instances, you can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service and its dependent components.
Name of the Collaboration Suite Database where the recorded message is stored. This is the Collaboration Suite Database where the message delivery test account is set up.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the Message Delivery Monitor Service. It provides a snapshot of how the Message Delivery Monitor Service instances are performing. If a particular metric is empty, it is likely that a Message Delivery Monitor Service instance is down and unavailable. Check the Up/Down status metric for all the Message Delivery Monitor 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.
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 79-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 |
> |
70 |
75 |
2 |
CPU utilization of Message Delivery Monitor Service, %target%, is %value%%% |
You can use this metric to determine if the Message Delivery Monitor Service is using the most CPU on your system, thereby leading to high end-user response times. If the Message Delivery Monitor 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 Message Delivery Monitor Service, the Voicemail and Fax Application that this Message Delivery Monitor 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.
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 79-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 |
> |
80 |
90 |
2 |
Memory utilization of Message Delivery Monitor Service, %target%, is %value%%% |
You can use this metric to determine if the Message Delivery Monitor Service is using the most memory on your system and leading to high end-user response times. If the Message Delivery Monitor 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 Message Delivery Monitor Service instances, the Voicemail and Fax Application that this Message Delivery Monitor 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.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the Message Delivery Monitor Service.
This metric is for internal use only.
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 Message Delivery Monitor Service. The Message Delivery Monitor Service shows a status of Down when all configured instances for this service are down.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
You can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service, specific instances of the Message Delivery Monitor Service, the Voicemail and Fax Application that this Message Delivery Monitor 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.
This category includes metrics that provide information about the Up/Down status of the Message Delivery Monitor Service.
This metric provides information about the Up/Down status of the Message Delivery Monitor Service and alerts you when the Message Delivery Monitor Service is down. The Message Delivery Monitor 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.
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 79-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 |
0 |
1 |
Message Delivery Monitor Service, %target%, is down |
You can restart the Message Delivery Monitor Service by selecting the Message Delivery Monitor 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 Message Delivery Monitor Service, specific instances of the Message Delivery Monitor Service, the Voicemail and Fax Application that this Message Delivery Monitor 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.
|
 Copyright © 2006, Oracle. All rights reserved. Legal Notices |
|
