| 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 Voicemail and Fax Application. A Voicemail and Fax Application is a set of services running on a host. There is one application per Telephony Server. The services are: Routing, Retrieval, Recording, Call Transfer, Message Delivery Monitor, Message Recovery, Telephony Monitor, SMDI (Simplified Message Desk Interface) Monitor, MWI (Message Waiting Indicator), IVR (Interactive Voice Response), and Fax Receiving. You may have multiple Voicemail and Fax Applications associated with a PBX-Application Cluster. You might require more than one Voicemail and Fax Application, for example, if a PBX requires more ports than one Telephony Server can support. From the Voicemail and Fax Application level, you get an overview of the status and performance of this application. The Voicemail and Fax Application inherits its properties from the global process settings set at the Voicemail and Fax component level and passes those settings on to its services. These settings can be overridden at the application level.
This category includes a set of metrics that provides information about the Up/Down status of the Collaboration Suite Database and the name of the host system where the Voicemail & Fax Application communicating with that database resides.
The Oracle Voicemail & Fax services process incoming calls and store the voice mail and fax messages recorded in each call in the called party's account in the Collaboration Suite Database.
This metric provides information about the Up/Down status of the Collaboration Suite Database which stores the voice mail and fax messages for users. It alerts you when the Collaboration Suite Database is down.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
0 |
1 |
Collaboration Suite Database is inaccessible |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Collaboration Suite Database Name" object.
If warning or critical threshold values are currently set for any "Collaboration Suite Database 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 "Collaboration Suite Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
If the Collaboration Suite Database is down, restart the database. Otherwise, restore connectivity between the Oracle Voicemail & Fax Application host and the Collaboration Suite Database named.
Host name of system where the the Voicemail & Fax Application is running. The application stores and retrieves voice mail and fax messages from the Collaboration Suite Database named.
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 99-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 |
Incorrect Accessing Host Name |
Multiple Thresholds
For this metric you can set different warning and critical threshold values for each "Collaboration Suite Database Name" object.
If warning or critical threshold values are currently set for any "Collaboration Suite 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 "Collaboration Suite Name" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
User Action
If the Oracle Voicemail & Fax Application host is down, bring up the host.
This category includes a set of metrics that provides the availability status of key features supported by the Oracle Voicemail & Fax Applications and its key dependent components in the Oracle Collaboration Suite.
This category provides information on the ability of Oracle Voicemail & Fax Applications to accept inbound faxes and to handle the recording and retrieval of voice mail and fax messages. In addition, the status of key dependent compoments in the Oracle Collaboration Suite (Collaboration Suite Database and Oracle Internet Directory) are also provided.
The Oracle Voicemail & Fax services process incoming calls based on profile and context information stored in the Oracle Internet Directory and stores the voice mail and fax messages recorded in each call in the called party's account in the Collaboration Suite Database.
The status of the Telephony Server is reported on the Voicemail & Fax Application Home page. Details on the status over various periods of time is reported in the All Metrics page of the Telephony Monitor Service.
This metric provides information about the Up/Down status of the Collaboration Suite Database which stores the voice mail and fax messages for users. It alerts you when the Collaboration Suite Database is down.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
Not all Collaboration Suite Database(s) accessible |
User Action
If the Collaboration Suite Database is down, restart the database. Otherwise, restore connectivity between the Oracle Voicemail & Fax Application host and the Collaboration Suite Database named.
The inbound fax feature is reported as available (status is Up) on the All Metrics page if at least one instance of each of the key Voicemail & Fax Application Services (Fax Receiving, Telephony Monitor, Routing) is Up. It is assumed that Oracle Internet Directory and all Collaboration Suite Databases used by the Application Services are Up.
Note that for the retrieval feature to be reported as available (status is Up) on the Oracle Voicemail & Fax Application home page, all the above conditions in the All Metrics page must hold. In addition, if SMDI is enabled, at least one instance of SMDI Monitor Service in each PBX-Application Cluster must be up.
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 99-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 |
0 |
1 |
Inbound Fax Feature is unavailable |
User Action
Check to see that at least one instance of each of the key Voicemail & Fax Application Services (Fax Receiving, Telephony Monitor, Routing) is Up. It is assumed that Oracle Internet Directory and all Collaboration Suite Databases used by the Application Services are Up.
You can restart a particular service by selecting that service target and clicking Restart on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by that service or specific instances of the service, by the Voicemail & Fax Application that this Fax Receiving Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), by the central agent on the host computer, or by the host computer.
This metric provides information about the Up/Down status of the Oracle Internet Directory. It alerts you when the Oracle Internet Directory is down.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
0 |
1 |
Oracle Internet Directory inaccessible |
User Action
If the Oracle Internet Directory is down, restart the Oracle Internet Directory database and its services. Otherwise, restore accessibility of Oracle Internet Directory service for the Oracle Voicemail & Fax Application.
The recording feature is reported as available (status is Up) on the All Metrics page if at least one instance of each of the key Voicemail & Fax Application services (Recording, Telephony Monitor, Routing) is Up. It is assumed that Oracle Internet Directory and all Collaboration Suite Databases used by the Application Services are Up.
Note that for the recording feature to be reported as available (status is Up) on the Oracle Voicemail & Fax Application home page, all the above conditions in the All Metrics page must hold. In addition, if SMDI is enabled, at least one instance of SMDI Monitor Service in each PBX-Application Cluster must be up.
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 99-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 |
Recording Feature is unavailable |
User Action
Check to see that at least one instance of each of the key Voicemail & Fax Application services (Recording, Telephony Monitor, Routing) is Up. If SMDI is enabled, check to see that at least one instance of SMDI Monitor Service is Up.
You can restart a particular service by selecting that service target and clicking Restart on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by that service or specific instances of the service, by the Voicemail & Fax Application that this Recording Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), by the central agent on the host computer, or by the host computer.
The retrieval feature is reported as available (status is Up) on the All Metrics page if at least one instance of each of the key Voicemail & Fax Application Services (Retrieval, Telephony Monitor, Routing) is Up, and Oracle Internet Directory and all Collaboration Suite Databases used by the Application Services are Up.
Note that for the retrieval feature to be reported as available (status is Up) on the Oracle Voicemail & Fax Application home page, all the above conditions for All Metrics page must be true. In addition, if SMDI is enabled, at least one instance of SMDI Monitor Service in each PBX-Application Cluster must be up.
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 99-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 |
0 |
1 |
Retrieval Feature is unavailable |
User Action
Check to see that at least one instance of each of the key Voicemail & Fax Application Services (Retrieval, Telephony Monitor, Routing) is Up, and Oracle Internet Directory and all Collaboration Suite Databases used by the Application Services are Up.
You can restart a particular service by selecting that service target and clicking Restart on the Oracle Voicemail and Fax home page. To investigate why the service is down, check for alerts that may have been generated by that service or specific instances of the service, by the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), by the central agent on the host computer, or by the host computer.
This category includes a set of metrics that provides information on the average performance and capacity of all services in this Voicemail & Fax Application.
In terms of performance, this category reports the average greeting response time for all Recording Service instances, as well as the average login response time, average menu play time, average message play time, and average message delivery time for all Retrieval Service instances in this Voicemail & Fax Application.
In terms of capacity, this category reports the total number of concurrent calls handled by all Retrieval, Recording and Fax Receiving Service instances in this Voicemail & Fax Application. In addition, this category also reports the total number of calls handled by all service instances in this Voicemail & Fax Application since the systems were first started up.
Average Greeting Response Time is the average greeting response time for this Voicemail and Fax Application, over the time period specified in the View Data field. Greeting response time is the length of time, in milliseconds, to hear the voice mail system greeting once the user has successfully logged in.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
Greeting Response Time exceeded |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Recording Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Recording Service instances, and resource shortage among key components in the instances.
To investigate why the greeting response time exceeded the response time value set, check for alerts that may have been generated by the Recording Service or specific instances of the Recording Service, the Routing Service, the Voicemail & Fax Application that this Recording Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to outages of specific recording instances, you can restart the Recording Service by selecting the Recording Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home pages of those components to view their Up/Down status. If you suspect resource contention is affecting components, review the resource usages of the Recording Service and its dependent components.
Average Login Response Time is the average login response time for this Voicemail and Fax Application, over the time period specified in the View Data field. Login response time is the length of time, in milliseconds, between the time the password is accepted and the voice mail system responds with the message count.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
Login Response Time exceeded |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the login response time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent component -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to outages of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home pages of those components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Menu Play Time is the average length of time it takes to play the Message Menu after the message count is played, for this Voicemail and Fax Application, over the time period specified in the View Data field. The time is measured in milliseconds.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
Menu Play Time exceeded |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the menu play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or by the host computer.
If you suspect that the cause of the high average response time is due to outages of specific retrieval instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home pages of those components to view their Up/Down status. If you suspect resource contention is affecting the components, review the resource usage of the Retrieval Service and its dependent components.
Average Message Delivery Time is the average message delivery time for this Voicemail and Fax Application, 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.
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 99-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 |
Message Delivery Time exceeded |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Message Delivery Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Message Delivery Service instances, and resource shortages 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 Service or specific instances of the Message Delivery Service, by the Voicemail & Fax Application that this Message Delivery Service is a member of (check the status of dependent components -- Oracle Internet Directory, Collaboration Suite Databases, Telephony Server), by the central agent on the host computer, or by the host computer.
If you suspect that the cause of the high average response time is due to outages of specific Message Delivery Service instances, you can restart the Message Delivery Service by selecting the Message Delivery 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 resource contention is affecting the components, review the resource usage of the Message Delivery Service and its dependent components.
Average Message Play Time is the message play time for this Voicemail and Fax Application over the time period specified in the View Data field. Message Play Time is the length of time between the time the user chooses to hear the message and when the message starts playing. The time is measured in milliseconds.
Metric Summary
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 99-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 |
Message Play Time exceeded |
User Action
Performance degradation can result from one or more causes, including but not limited to: outage of one or more Retrieval Service instances, outage of one or more key components in the instances, contention for common resources (for example, Oracle Internet Directory) among Retrieval Service instances, and resource shortage among key components in the instances.
To investigate why the message play time exceeded the response time value set, check for alerts that may have been generated by the Retrieval Service or specific instances of the Retrieval Service, the Routing Service, the Collaboration Suite Databases, the Voicemail & Fax Application that this Retrieval Service is a member of (check the status of dependent components -- Oracle Internet Directory, Telephony Server, Collaboration Suite Databases), the central agent on the host computer, or the host computer.
If you suspect that the cause of the high average response time is due to outages of specific Retrieval Service instances, you can restart the Retrieval Service by selecting the Retrieval Service target and clicking Restart on the Oracle Voicemail & Fax home page.
If you suspect that outages of other key components are affecting performance, navigate to the home pages of those components to view their Up/Down status. If you suspect resource contention is affecting components, review the resource usage of the Retrieval Service and its dependent components.
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.
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 99-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 |
Current Calls overload |
User Action
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.
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.
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 99-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 |
Total Calls overload |
User Action
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 Voicemail and Fax Application. It provides a snapshot of how the Voicemail and Fax Application is performing. If a particular metric is empty, it is likely that the Voicemail and Fax Application is down and unavailable. Check the Up/Down status metric for the application, its services, and their instances.
This metric represents the percentage of the host CPU recorded for the Voicemail and Fax Application. 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 99-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 |
> |
70 |
75 |
2 |
CPU utilization of Voicemail and Fax Application, %target%, is %value%%% |
User Action
You can use this metric to determine if the Voicemail and Fax Application is using the most CPU on your system, thereby leading to high end-user response times. If the Voicemail and Fax Application 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: Voicemail and Fax Application's member services and their instances, the central agent on the host computer, or the host computer. Also, check the status of dependent components - Oracle Internet Directory, Telephony Server.
This metric shows you the percentage of host memory being used by the Voicemail and Fax Application. 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 99-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 |
> |
80 |
90 |
2 |
Memory utilization of Voicemail and Fax Application, %target%, is %value%%% |
User Action
You can use this metric to determine if the Voicemail and Fax Application is using the most memory on your system and leading to high end-user response times. If the Voicemail and Fax Application 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: Voicemail and Fax Application's member services and their instances, the central agent on the host computer, or the host computer. Also, check the status of dependent components - Oracle Internet Directory, Telephony Server.
This metric represents the memory usage (in megabytes) for the Voicemail and Fax Application
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 Voicemail and Fax Application.
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 Voicemail and Fax Application and alerts you when the application is down. The Voicemail and Fax Application shows a status of Down when any one of the enabled services for this application is down. If the status is down, it could mean that the services instances configured for this application are in the process of starting up, or they are 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.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
User Action
You can restart the Voicemail and Fax Application by selecting the Voicemail and Fax Application target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the target is down, check for alerts that may have been generated by the following: Voicemail and Fax Application's member services and their instances, the central agent on the host computer, or the host computer. Also, check the status of dependent components - Oracle Internet Directory, Telephony Server.
This category includes metrics that provide information about the Up/Down status of the Voicemail and Fax Application.
This metric provides information about the Up/Down status of the Voicemail and Fax Application and alerts you when the application is down. The Voicemail and Fax Application shows a status of Down when any one of the enabled services for this application is 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 99-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 |
0 |
1 |
Voicemail and Fax Application, %target%, is down |
User Action
You can restart the Voicemail and Fax Application by selecting the Voicemail and Fax Application target and clicking on the Restart button on the Oracle Voicemail and Fax home page. To investigate why the target is down, check for alerts that may have been generated by the following: Voicemail and Fax Application's member services and their instances, the central agent on the host computer, or the host computer. Also, check the status of dependent components - Oracle Internet Directory, Telephony Server.
