|
Oracle® Enterprise Manager Metric Reference Manual
10g Release 1 (10.1) Part No. B12015-01 |
|
|
|
|
This metric will monitor the top 10 calendar processes sorted in descending order on CPU consumption followed by memory consumption.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
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.
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 the Editing Thresholds topic in the Enterprise Manager online help for information on accessing the Edit Thresholds page.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the disk space on which the calendar db resides. A threshold is set for the availability of this disk space. If the calendar db is mounted on a shared disk then this metric will not reflect calendar db usage alone but it will reflect the shared usage of the calendar and all other applications mounted on this disk.
This metric will monitor the top 10 calendar processes sort in descending order on CPU consumption followed by memory consumption.
This metric will monitor the top 10 calendar processes sorted in descending order on CPU consumption followed by memory consumption.
This metric will monitor the top 10 calendar processes sorted in descending order on CPU consumption followed by memory consumption.
This metric will monitor the top 10 calendar processes sorted in descending order on CPU consumption followed by memory consumption.
This metric will monitor the top 10 calendar processes sorted in descending order on CPU consumption followed by memory consumption.
Displays the number of calendar connections.
Total number of dedicated connections: Connections made by desktop clients such as CorporateTime, Oracle Outlook Connector or any calendar SDK based application.
Total number of reserved connections: connections made by the server internally. Mainly made by the SNC engine and the CWS. If the calendar server has multiple nodes then the reserved number of calendar connections should proportional to the number of node network connections. 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 20-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 | 2 | 1 | Not Defined |
Total number of shared connections: Connections made by web based applications.
Current wireless notification/reminder requests in the queue. Threshold is set for this metric if it is too high.
Current wireless notification/reminder requests in the queue. 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 20-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 | 100 | 1 | Not Defined |
Current mail notification/reminder requests in the queue. 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 20-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 | 100 | 1 | Not Defined |
Current node-to-node event replications requests in the queue. 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 20-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 | 100 | 1 | Not Defined |
Current requests for imeeting items in the queue. 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 20-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 |
Displays the number of requests in the CWS queue.
Displays the number of mail requests 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 20-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 |
Mail notification requests already processed over the past X minutes since the agent contacted the calendar server.
Displays the number of node-to-node Replication request 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 20-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 |
Displays the number of node-to-node Replication requests processed.
Displays the number of server side requests 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 20-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 |
Server Side Reminder requests processed.
Wireless requests errors processed.
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 20-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 | 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. Returns:
Severity status code | Status
where:
Severity is: 0-Normal, 1-Warning, 2-Error.
Threshold is set for this metric if it 1 or 2.
Status is Up, Down, Partially Up, Inconsistent, and Stand By
Up has a Severity 0
Partially Up, Stand By have a Severity 1
Partially Up: means that the main daemons (eng, lck) are up but one of the other daemons maybe down (cws, snc, das)
Stand By: means that the server is shut down but the calendar server manager CSM is up.
Down, Inconsistent have Severity 2
Inconsistent: means that either the lck daemon or the main engine is down.
Displays the status of the calendar server.
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.
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.
Total transaction time excluding authentication time: total transaction time after subtracting user authentication time.
Total transaction time excluding connection time: total transaction time after subtracting connection time.
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.
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 20-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 | > | 10000 | 20000 | 1 | Not Defined |