The E-Mail IMAP Service target allows you to monitor the availability and responsiveness of the Oracle Email IMAP Service to client requests. This target is monitored by periodically performing client-like protocol operations in order to determine whether the IMAP Service is available and responding in a reasonable time. This target must be configured manually to refer to the host name and port number that clients use to connect to the Oracle Email IMAP Service. The IMAP Service can be running on a single host or, in large installations, behind a network load balancer or network address translator.
This metric category captures the response characteristics of the Oracle Email IMAP service as seen by a client application.
This metric shows the time it takes for the IMAP server to accept a network connection from a client. It also reflects the performance of the Oracle Net Services Listener.
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 47-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 |
> |
100 |
2000 |
2 |
Time taken to connect to mail service is %value% (ms) |
This metric shows the time it takes for a connected client to log in 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 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 47-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 |
> |
2000 |
5000 |
2 |
Time taken to login is %value% (ms) |
This metric indicates whether clients are able to access e-mail through the IMAP Service. At least one IMAP server and Oracle Net Services Listener must be running in order for the IMAP Service to be available.
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 47-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 |
Failed to connect to IMAP service |
The IMAP Service logically consists of the Oracle Email IMAP Server and an associated Oracle Net Services Listener listening for IMAP network connection requests. If this service is down, check to see if at least one IMAP server process is running. Also check to see if the Oracle Net Services Listener configured for the Oracle Email system is running.
This metric shows the 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 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 47-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 |
> |
2000 |
5000 |
2 |
Time taken to list folders is %value% (ms) |
This metric shows the time it takes 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 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 47-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 |
> |
2000 |
5000 |
2 |
Time taken to read an e-mail is %value% (ms) |
This metric shows the total time it takes for one simulated IMAP session. This metric is directly dependent on the performance characteristics of the IMAP Server target.
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 47-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 |
> |
5000 |
10000 |
2 |
Total Time taken to read an e-mail is %value% (ms) |
To reduce the total response time, tune your IMAP servers after observing their performance levels. You can also identify which operations in a client session are taking significant time to complete by looking at the other columns in this metric.