| 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 |
The Mail IMAP Service monitors the availability, performance, and usage of the IMAP functionality provided by the underlying Mail system.
The Bytes Transferred category provides information about the data transferred between IMAP Server and IMAP Clients.
Note:
For target Version 1.0, the collection frequency for each metric is every 15 minutes.The following table lists the metrics and their descriptions.
Table 61-1 Bytes Transferred Metrics
| Metric | Description |
|---|---|
|
Bytes Received By Server |
Measures the amount of data received by the IMAP Server from the IMAP Clients. It includes data related to normal IMAP commands and data due to messages appended back to the server, typically to the "Sent" or "Sent Items" folder. This value is the sum of all the data received by the IMAP Redundancy Groups. |
|
Bytes Sent By Server |
Measures the amount of data sent to IMAP clients by the IMAP Server. The data includes mail and IMAP responses. This value is the sum of all the data sent by the IMAP Redundancy Groups. |
The Client Connections category provides information about the client connections on the IMAP Server.
This metric shows the total number of client connections open on the IMAP Server. The value is the sum of all open connections for IMAP Redundancy Groups.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| Version 1.0 | Every 15 minutes |
The Fetch Details category charts the rate of FETCH commands requested by all clients of IMAP Server instances on this target over the collection period. An IMAP client will use the FETCH command to get most types of message data from an Oracle Collaboration Suite Database, including message identifiers, header information, messages, and message body parts.
This informational metric represents the rate of FETCH commands occurring over a period of time. This rate should vary proportionally to the number and type of mail clients concurrently connected. Changes in this value can be caused by a "rogue" client or by users changing from one type of mail client to another. The FETCH commands rate indicates the usage patterns and resource requirements of the mail system. This rate is the sum of all the fetch count values of all IMAP Redundancy Groups.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| Version 1.0 | Every 15 minutes |
The IMAP Response category captures the response characteristics of the Oracle Mail IMAP service as seen by a client application.
Note:
For target Version 1.0, the collection frequency for each metric is every 15 minutes.The following table lists the metrics and their descriptions.
Table 61-2 IMAP Response Metrics
| Metric | Description |
|---|---|
|
Connect Time (ms) |
Time taken for the IMAP server to accept a network connection from a client. It also reflects the performance of the Oracle Net Services Listener. The connection time is the value determined by the Beacon(s) monitoring this service. The Beacon(s) is(are) responsible for executing the perl script to ping the host and determine the total connection time. If multiple Beacons are monitoring this service, the value displayed is the average of all the values determined by all the Beacons. |
|
IMAP Timing (ms) |
Total time taken for one simulated IMAP session. This metric is directly dependent on the performance characteristics of the IMAP Server target. The timing is the value determined by the Beacon(s) monitoring this service. The Beacon(s) is(are) responsible for executing the perl script to ping the host and determine the total time. If multiple Beacons are monitoring this service, the value displayed is the average of all the values determined by all the Beacons. |
|
Login Time (ms) |
Time taken for a connected client to login to the IMAP Server. It is also indicative of the Oracle Internet Directory response time because clients are authenticated against the Oracle directory server. The login time is the value determined by the Beacon(s) monitoring this service. The Beacon(s) is(are) responsible for executing the perl script to ping the host and determine the total login time. If multiple Beacons are monitoring this service, the value displayed is the average of all the values determined by all the Beacons. |
|
Status |
Indicates whether or not clients are able to access Mail through the IMAP Service. The availability depends upon the status determined by the Beacon monitoring this service. If the Status of Mail IMAP Service is down, then check the results obtained by Root Cause Analysis on the Mail IMAP Service Home Page. |
|
Status Message |
Describes the status. If the Mail IMAP Service is down, this metric shows why the service is down. The availability depends upon the status determined by the Beacon monitoring this service. |
|
Time to List Folders (ms) |
Time it takes to retrieve a user's folder list from the Oracle Collaboration Suite Database (mailstore) through the IMAP server. The folder list includes the Shared and Public folders that a user has access to. This metric is also indicative of the database and directory performance. The timing is the value determined by the Beacon(s) monitoring this service. The Beacon(s) is(are) responsible for executing the perl script to ping the host and determine the total connection time. If multiple Beacons are monitoring this service, the value displayed is the average of all the values determined by all the Beacons. |
|
Time to Read Email (ms) |
Time taken to retrieve a message from the Oracle Collaboration Suite Database (mailstore) through the IMAP server. This metric is also indicative of the database performance. The timing is the value determined by the Beacon(s) monitoring this service. The Beacon(s) is(are) responsible for executing the perl script to ping the host and determine the total time. If multiple Beacons are monitoring this service, the value displayed is the average of all the values determined by all the Beacons. |
The IMAP Service Response category captures the response characteristics of the Oracle Mail IMAP service as seen by a client application.
This metric indicates whether or not clients are able to access Mails through the IMAP Service. The availability of IMAP Service depends upon the status determined by the Beacon monitoring this service.
If the Status of Mail IMAP Service is not up, then check the results obtained by Root Cause Analysis on the Mail IMAP Service Home Page.
The Response Time category provides information about the average time taken to login and read the messages from IMAP Server.
This metric shows the average time taken to login to the IMAP Server.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| Version 1.0 | Every 15 minutes |
This metric shows the average time taken to retrieve a message from the Oracle Collaboration Suite Database (mailstore) through the IMAP server.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| Version 1.0 | Every 15 minutes |
The Security category provides information about security related activities.
This metric shows the connections refused by the IMAP Server. The value is the sum of all the connections refused by the IMAP Redundancy Groups.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| Version 1.0 | Every 15 minutes |
|
 Copyright © 2006, Oracle. All rights reserved. Legal Notices |
|
