This metric will monitor the ten most active calendar processes sorted in descending order on CPU consumption followed by memory consumption.
This metric will monitor the disk space where the Oracle Calendar database resides. A threshold is set for the availability of this disk space. If the Oracle Calendar database is mounted on a shared disk, this metric will not reflect just the Oracle Calendar database, but the shared usage of the Oracle Calendar database and all other applications mounted on the disk.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics and their descriptions.
Table 3-1 Calendar DB Size Metrics
| Metric | Description |
|---|---|
|
% Disk Space Available |
|
|
Filesystem |
Filesystem type where the Oracle Calendar server is installed |
|
Mounted on |
Mounted drive or directory on which the Oracle Calendar server is located |
|
Total Disk Space (MB) |
Total disk size of this filesystem, in megabytes |
|
Total Size (MB) |
Total size of the Oracle Calendar server database, in megabytes |
|
Total Space Free (MB) |
Total disk space available in the filesystem where the Oracle Calendar server is installed |
|
Total Space Used (MB) |
Total space used in the filesystem where the Oracle Calendar server is installed |
The percent of total space available on the filesystem where the Oracle Calendar server is installed.
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 3-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 |
< |
10 |
5 |
1 |
Not Defined |
For this metric you can set different warning and critical threshold values for each "DB Directory" object.
If warning or critical threshold values are currently set for any "DB Directory" 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 "DB Directory" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric will monitor the ten most active Oracle Calendar server processes, sorted in descending order based on CPU consumption, followed by memory consumption.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics and their descriptions.
Table 3-3 Calendar Server Top Processes Metrics
| Metric | Description |
|---|---|
|
CPU Time |
Will monitor the percentage of CPU consumption used by the ten most active calendar server processes |
|
Elapsed Time |
Elapsed time since the associated Oracle Calendar server process was started, in the form: [[dd-]hh:]mm:ss where dd is the number of days, hh is the number of hours, mm is the number of minutes and ss is the number of seconds This will be displayed for the ten most active processes collected. |
|
Memory Size (MB) |
Total size, in kilobytes, of the associated Oracle Calendar server process in virtual memory. This will be displayed for the ten most active processes collected. |
|
PID |
Decimal value of the Oracle Calendar server process ID. This will be displayed for the ten most active processes collected. |
This metric collects information about the number of connections made to the calendar server system.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics and their descriptions.
| Metric | Description |
|---|---|
|
Number of Dedicated Connections |
Total number of dedicated connections, including connections made by desktop clients such as Oracle Calendar, Oracle Connector For Outlook, or any calendar SDK based application. |
|
Number of Reserved Connections |
|
|
Number of Shared Connections |
Total number of shared connections made by web based applications, such as the Oracle Calendar Web client interface and Oracle Calendar Sync. These applications establish a connection pool to the calendar server that is shared among all connected users. |
|
Total Number of Calendar Connections |
Total number of connections made to the calendar server of any type. |
The total number of reserved connections made by the server internally, usually relating the SNC engine and the CWS. If the calendar server has multiple nodes, then the reserved number of calendar connections should be proportional to the number of node network connections. A threshold is set for this metric if the value is too low.
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 3-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 |
2 |
1 |
Not Defined |
The number of wireless notification/reminder requests currently in the queue. A threshold is set for this metric if it is too high.
The number of wireless notification/reminder requests currently in the queue. A threshold is set for this metric if the value is too high.
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 3-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 |
100 |
1 |
Not Defined |
The number of node-to-node replication requests currently in the queue. A threshold is set for this metric if the value is too high.
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 3-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 |
100 |
1 |
Not Defined |
The number of node-to-node event replications requests currently in the queue. A threshold is set for this metric if it is too high.
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 3-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 |
100 |
1 |
Not Defined |
The number of requests for Web Conference items currently in the queue. A threshold is set for this metric if the value is too high.
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 3-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 |
100 |
1 |
Not Defined |
This metric provides information about the cumulative number of requests processed by the CWS.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics and their descriptions.
Table 3-10 CWS Cumulative Queue Stats Metrics
| Metric | Description |
|---|---|
|
Mail Requests Errors |
|
|
Mail Requests Processed |
Number of mail notification requests processed successfully, since the last interval, by the CWS |
|
Replication Requests Errors |
|
|
Replication Requests Processed |
Total number of node-to-node Replication requests successfully processed by the CWS |
|
SSR Requests Errors |
|
|
SSR Requests Processed |
Total number of Server Side Reminder requests successfully processed by the CWS |
|
Wireless Requests Errors |
|
|
Wireless Requests Processed |
Total number of wireless notification requests successfully processed by the CWS |
The number of mail requests processed by the CWS that contain errors.
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 3-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 |
100 |
1 |
Not Defined |
The total number of node-to-node Replication requests processed by the CWS that contain errors.
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 3-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 |
100 |
1 |
Not Defined |
The total number of Server Side Reminder requests processed by the CWS that contain errors.
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 3-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 |
100 |
1 |
Not Defined |
The number of errors in the processed wireless requests.
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 3-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 |
100 |
1 |
Not Defined |
Total transaction time for sending 64Kb of data to the calendar server and receiving a reply back (tests all nodes). This transaction time includes connecting and authenticating to the server.
Displays the status of the calendar server and returns a status of Up, Partially Up or Down
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
The status code of the calendar server. Status code 0 indicates a normal calendar server status. Status code 1 indicates the calendar server is running, but partially. Status code 2 indicates the calendar server is either down or running inconsistently.
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.
This metric is used to calculate the response time of the calendar server.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics and their descriptions.
Table 3-16 Response Time (64 Kb) Metrics
| Metric | Description |
|---|---|
|
Time Excluding Authentication OH (ms) |
Total transaction time, excluding authentication, for sending 64Kb of data to the calendar server and receiving a reply (tests all nodes |
|
Time Excluding Connection OH (ms) |
Total transaction time, excluding connection time, for sending 64Kb of data to the calendar server and receiving a reply (tests all nodes |
|
Total Transaction Time (ms) |
The total transaction time, including authentication, for sending 64Kb of data to the calendar server and receiving a reply (tests all nodes).
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 3-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 |
> |
10000 |
20000 |
1 |
Not Defined |