| 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 SMDI (Simplified Message Desk Interface) Monitor Service. The SMDI Monitor Service provides an interface between SMDI-enabled PBXes and Oracle Voicemail and Fax. It processes call detail messages from the PBX and passes them to the Routing Service. It also receives MWI (Message Waiting Indicator) requests from the MWI Service and dispatches these requests to the PBX.
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the SMDI Monitor Service instance. It provides a snapshot of how the SMDI 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 SMDI Monitor Service instance.
This metric represents the percentage of the host CPU recorded for this instance of the SMDI 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.
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 96-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 |
> |
70 |
75 |
2 |
CPU utilization of SMDI Monitor Instance, %target% (%Name%), is %value%%% |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Name" object.
If warning or critical threshold values are currently set for any "Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
You can use this metric to determine if the SMDI 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 SMDI Monitor Service instance, the Voicemail and Fax Application that this SMDI Monitor Service instance is a member of (check the status of dependent components - Internet Directory, Telephony Server), or the host computer.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric shows you the percentage of host memory being used by the SMDI 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.
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 96-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 |
> |
80 |
90 |
2 |
Memory utilization of SMDI Monitor 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 SMDI 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 SMDI Monitor Service instance, the Voicemail and Fax Application that this SMDI Monitor Service instance is a member of (check the status of dependent components - Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the SMDI Monitor 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 SMDI Monitor 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 SMDI Monitor Service instance and alerts you when the SMDI 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.
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 96-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 |
0 |
1 |
SMDI Monitor 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 SMDI Monitor Service by selecting the SMDI 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 SMDI Monitor Service instance, the Voicemail and Fax Application that this SMDI Monitor Service instance is a member of (check for dependent component status - Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the SMDI Monitor Service. It provides a snapshot of how the SMDI Monitor Service instances are performing. If a particular metric is empty, it is likely that an SMDI Monitor Service instance is down and unavailable. Check the Up/Down status metric for all the SMDI 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.
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 96-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 |
> |
70 |
75 |
2 |
CPU utilization of SMDI Monitor Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the SMDI Monitor Service is using the most CPU on your system, thereby leading to high end-user response times. If the SMDI 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 SMDI Monitor Service, the Voicemail and Fax Application that this SMDI Monitor Service is a member of (check the status of dependent components - Internet Directory, Telephony Server), or the host computer.
This metric shows you the percentage of host memory being used by the service. By default, a critical and warning threshold value is set for this metric column. Alerts are generated when threshold values are reached. You can edit the value for a threshold as required.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 96-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 |
> |
80 |
90 |
2 |
Memory utilization of SMDI Monitor Service, %target%, is %value%%% |
User Action
You can use this metric to determine if the SMDI Monitor Service is using the most memory on your system and leading to high end-user response times. If the SMDI 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 SMDI Monitor Service instances, the Voicemail and Fax Application that this SMDI Monitor Service is a member of (check the status of dependent components - Internet Directory, Telephony Server), or the host computer.
This metric represents the memory usage (in megabytes) for the service.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
Compare this metric with Memory Usage (%), which measures the percentage of host memory being used by the SMDI Monitor Service.
This metric is for internal use only.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
This metric provides information about the Up/Down status of the SMDI Monitor Service. The SMDI Monitor Service shows a status of Down when all configured instances for this service are down.
Metric Summary
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
You can restart the SMDI Monitor Service by selecting the SMDI 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 SMDI Monitor Service, specific instances of the SMDI Monitor Service, the Voicemail and Fax Application that this SMDI Monitor Service is a member of (check for dependent component status - Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category contains metrics that provide information about the Up/Down status of the SMDI Monitor Service.
This metric provides information about the Up/Down status of the SMDI Monitor Service and alerts you when the SMDI Monitor Service is down. The SMDI 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.
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 96-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 |
0 |
1 |
SMDI Monitor Service, %target%, is down |
User Action
You can restart the SMDI Monitor Service by selecting the SMDI 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 SMDI Monitor Service, specific instances of the SMDI Monitor Service, the Voicemail and Fax Application that this SMDI Monitor Service is a member of (check for dependent component status - Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
