Lists the metrics for the Oracle Calendar application system processes.
Monitors the availability of the disk space where the OCAS/sessiondb and OCAS/linkdb exist. The threshold is set if the availabilities are less than 10% and 5%, respectively.
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 2-1 Calendar Applications DB Size Metrics
| Metric | Description |
|---|---|
|
% Disk Space Available |
|
|
Filesystem |
Name of the filesystem where the Oracle Calendar application system is installed |
|
Mounted on |
Mounted drive or directory where the Oracle Calendar application system is located |
|
Total Disk Space (Kb) |
Total space in the filesystem where the Oracle Calendar application system is installed |
|
Total Size (Mb) |
Total database size of the Oracle Calendar application system, in megabytes |
|
Total Space Free (Kb) |
Total available space in the filesystem where the Oracle Calendar application system is installed |
|
Total Space Used (Kb) |
Total space used in the filesystem where the Oracle Calendar application system is installed |
The percentage of total space used on the file system where the Oracle Calendar application system 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 2-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 list the following Oracle Calendar application system processes:
1= CPU Time
1= Memory Usage
2= Elapsed time since the start of the process
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 2-3 Calendar Applications Processes Info Metrics
| Metric | Description |
|---|---|
|
CPU Time |
CPU consumption percentage of the Oracle Calendar application system process. This will be displayed for the ten most active processes collected |
|
Elapsed Time |
Elapsed time since the associated Oracle Calendar application system 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 (Kb) |
|
|
PID |
Decimal value of the Oracle Calendar application system process ID. This will be displayed for the ten most active processes. |
In kilobytes, the total size of the associated Oracle Calendar application system process in virtual memory. This will be displayed for the ten most active processes collected.
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 2-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 |
50000 |
1 |
Not Defined |
For this metric you can set different warning and critical threshold values for each "Calendar Process" object.
If warning or critical threshold values are currently set for any "Calendar Process" 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 "Calendar Process" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This metric displays the response time of reaching the Systems web page of the Oracle Calendar application system.
The response time, in milliseconds, of reaching the Systems page of the Oracle Calendar application system.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| All Versions | Every 5 Minutes |
Depending on the response time, the status of the Oracle Calendar application system is set. A threshold is set for this metric if it is not 0.
0= Okay
1= Timed out
2= The service is probably 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.