The E-Mail SMTP Inbound Service target allows you to monitor the availability and responsiveness of the Oracle Email SMTP Inbound Service to client requests. This target is monitored by periodically performing client-like protocol operations to determine whether the SMTP Inbound 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 SMTP Inbound Service. The SMTP Inbound 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 SMTP Inbound Service as seen by a client application.
This informational metric shows the time taken since the last collection of this data for the SMTP Inbound Server to accept a network connection from a client. It is also indicative of the performance of the Oracle Net Services Listener. This metric is aggregated into the Total Time Metric.
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 54-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 |
> |
1000 |
2000 |
2 |
Time taken to connect to SMTP service is %value% (ms) |
This indicates whether clients can access e-mail through the SMTP Inbound Service. At least one SMTP Inbound Server and Oracle Net Services Listener must be running in order for the SMTP Inbound 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 54-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 |
0 |
1 |
Failed to connect to SMTP service |
The SMTP Inbound Service logically consists of the Oracle Email SMTP Inbound Server and an associated Oracle Net Services Listener listening for SMTP Inbound network connection requests. If this service is down, check to see if at least one SMTP Inbound Server process is running. Also check to see if the Oracle Net Services Listener configured for the Oracle Email system is running.
This informational metric shows the time taken since the last collection of this data for the SMTP server to accept a message for delivery or relay. If the SMTP Servers are not running in 'Submit' mode, this also shows the time it takes for a message to reach the recipient. The time required for Recipient lookup against the Oracle directory server and the time required to store a message in the Oracle Collaboration Suite Database is also a factor in the time indicated by this metric. This metric is aggregated into the Total Time Metric.
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 54-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 |
> |
2000 |
5000 |
2 |
Time taken to transfer e-mail is %value% (ms) |
This metric shows the total time taken since the last collection of this data to complete one simulated SMTP Inbound session. This metric is directly dependent on the performance characteristics of the SMTP Inbound 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 54-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 |
Total Time taken to send e-mail is %value% (ms) |
To reduce the total response time, tune the SMTP Inbound Servers after observing their performance levels. You can also identify which operations in a client session are taking excessive amounts of time by looking at the other columns in this metric.