| 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 Telephony Monitor Service. The Telephony Monitor Service monitors the Telephony Server and reports the status and some key metrics of the Telephony Server to the Enterprise Manager. It periodically checks the status of the Telephony Server and the number of active calls handled by the server.
This category includes a set of metrics that provides information about the status of this Telephony Server instance as well as the number of current and total telephony calls serviced by this Telephony Server instance.
The current number of calls is the concurrent number of telephony calls handled by this Telephony Server instance, over the time period specified in the View Data field.
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 97-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 |
Current Calls overload |
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.
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Telephony Monitor Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
Host name of system where Telephony Server instance is running.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Name of the metric.
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 Telephony Server instance. The Telephony Server instance shows a status of Down when the instance for this service is down.
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 97-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 |
0 |
1 |
Telephony Server Instance Is Down |
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.
The total number of calls is the total number of telephony calls handled by this Telephony Server instance, since the instance was started, over the time period specified in the View Data field.
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 97-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 |
Total Calls overload |
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.
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Telephony Monitor Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
This category includes a set of related metrics that provide you with information about the CPU and memory being used by the Telephony Monitor Service instance. It provides a snapshot of how the Telephony 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 Telephony Monitor Service instance.
This metric represents the percentage of the host CPU recorded for this instance of the Telephony 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 97-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 Telephony 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 Telephony 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 Telephony Monitor Service instance, the Voicemail and Fax Application that this Telephony 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 Telephony 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 97-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 Telephony 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 Telephony 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 Telephony Monitor Service instance, the Voicemail and Fax Application that this Telephony 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 Telephony 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 Telephony 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 Telephony Monitor Service instance and alerts you when the Telephony 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 97-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 |
Telephony 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 Telephony Monitor Service by selecting the Telephony 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 Telephony Monitor Service instance, the Voicemail and Fax Application that this Telephony Monitor Service instance is a member of (check the dependent component status - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category includes a set of related metrics that provides you with information about the CPU and memory being used by the Telephony Monitor Service. It provides a snapshot of how the Telephony Monitor Service instances are performing. If a particular metric is empty, it is likely that a Telephony Monitor Service instance is down and unavailable. Check the Up/Down status metric for all the Telephony 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 97-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 |
> |
70 |
75 |
2 |
CPU utilization of Telephony Monitor Service, %target%, is %value%%% |
You can use this metric to determine if the Telephony Monitor Service is using the most CPU on your system, thereby leading to high end-user response times. If the Telephony 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 Telephony Monitor Service, the Voicemail and Fax Application that this Telephony 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 97-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 |
> |
80 |
90 |
2 |
Memory utilization of Telephony Monitor Service, %target%, is %value%%% |
You can use this metric to determine if the Telephony Monitor Service is using the most memory on your system and leading to high end-user response times. If the Telephony 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 Telephony Monitor Service instances, the Voicemail and Fax Application that this Telephony 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 Telephony 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 Telephony Monitor Service. The Telephony 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 Telephony Monitor Service by selecting the Telephony 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 Telephony Monitor Service, specific instances of the Telephony Monitor Service, the Voicemail and Fax Application that this Telephony Monitor Service is a member of (check the dependent component status - 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 Telephony Monitor Service.
This metric provides information about the Up/Down status of the Telephony Monitor Service and alerts you when the Telephony Monitor Service is down. The Telephony 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 97-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 |
0 |
1 |
Telephony Monitor Service, %target%, Is Down |
You can restart the Telephony Monitor Service by selecting the Telephony 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 Telephony Monitor Service, specific instances of the Telephony Monitor Service, the Voicemail and Fax Application that this Telephony Monitor Service is a member of (check the dependent component status - Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
This category includes a set of metrics that provides summary information about the status of the Telephony Server instances as well as the number of current and total telephony calls serviced by the Telephony Server instances.
The current number of calls is the number of concurrent telephony calls handled by all the Telephony Server instances over the time period specified in the View Data field.
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 97-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 |
Current Calls overload |
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Telephony Monitor Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
This metric provides information about the Up/Down status of the Telephony Server Service. The Telephony Server 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 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 97-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 |
0 |
1 |
Telephony Server Service Is Down |
The total number of calls is the total number of telephony calls handled by all the Telephony Server instances, since the instances were started, over the time period specified in the View Data field.
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 97-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 |
Total Calls overload |
No action is required. If there is evidence that the service cannot keep up with the incoming call demand, return to the Telephony Monitor Service home page, click the Add One Instance button to increase the number of service instances that can handle the calls.
|
 Copyright © 2006, Oracle. All rights reserved. Legal Notices |
|
