The E-Mail NNTP Service target allows you to monitor the Oracle Email system at the service level. This target is monitored by automatically performing client-like protocol operations in order to to monitor whether the NNTP 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 is used to connect to the Oracle Email NNTP Service address. The NNTP service can be running from a single host or, in large installations, behind a network load balancer or network address translator.
The metrics in this category capture the response characteristics of the Oracle Email NNTP service as seen by a client application.
This metric shows the time taken for the NNTP server to accept a network connection from a client. It is also indicative of 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 51-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 to connect to news service is %value% (ms) |
None. This is for informational purposes only. This metric is aggregated into the Total Time Metric.
This metric shows whether newsgroup clients are able to access newsgroup articles via the NNTP Service. At least one NNTP service and Oracle Net Services Listener must be running in order for the NNTP 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 51-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 NNTP service |
The NNTP Service logically consists of the Oracle Email NNTP Server and an associated Oracle Net Services Listener which listens for NNTP network connection requests. If this service is down, check to see if at least one NNTP 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 taken to post a message to a newsgroup through the NNTP server. This metric is also indicative of database performance because news messages are stored in the Oracle Collaboration Suite Database (mailstore).
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 51-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 to post article is %value% (ms) |
None. This is for informational purposes only. This metric is aggregated into the Total Time Metric.
This metric shows the time taken to retrieve a message from the Oracle Collaboration Suite Database (mailstore) through the NNTP server. This metric is also indicative of database performance.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 5 minutes |
None. This metric is for informational purposes only. This metric is aggregated into the Total Time Metric.
This metric shows the total time taken to complete one simulated NNTP session. This metric is directly dependent on the performance characteristics of the NNTP 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 51-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 to post article is %value% (ms) |
To reduce the total response time, tune the NNTP servers after observing their performance levels. You can also identify which operations in a client session are taking time by looking at the other columns in this metric.