The Network News Transfer Protocol (NNTP) Inbound Server target provides session-oriented access for Internet Standards Based news clients. The metric categories provide statistical information on these NNTP servers.
This category includes metrics that provide information about messages for your NNTP Inbound Servers.
This indicates the rate at which messages are being posted to news groups. This metric is primarily informational and indirectly indicates the message insertion load placed on the Oracle Collaboration Suite Database.
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 50-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 10 Minutes |
After Every Sample |
> |
100 |
500 |
1 |
The messages posting rate is %value% messages/minute |
Sustained high values may indicate either a high traffic system, which is normal and requires no action, or a possible security breach which should be further investigated.
This metric indicates the rate at which messages are being retrieved from news groups in your system. This metric is primarily informational and indirectly indicates the load placed on the Oracle Collaboration Suite Database and the server message cache.
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 50-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 10 Minutes |
After Every Sample |
> |
100 |
500 |
1 |
The messages retrieval rate is %value% messsages/ minute |
Sustained high values may indicate either a high traffic system, which is normal and requires no action, or a possible security breach which should be further investigated.
This category includes network related metrics for the NNTP Inbound Server.
This metric represents the rate of connections opened to the NNTP_IN Server per minute.
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 50-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 10 Minutes |
After Every Sample |
> |
50 |
100 |
1 |
The rate of inbound NNTP connections is %value% connections/minute |
Sustained high values may indicate a possible security breach (denial-of-service attack) on your system and should be further investigated. Check the NNTP server log files for any rejected connections. Use esd_logscan.pl to scan the server log files.
This metric represents a gauge that counts the number of open connections to the NNTP Inbound Server. The counter is increased by one as soon as a connection request comes in and is decreased by one when a connection is closed.
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 50-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 10 Minutes |
After Every Sample |
> |
500 |
1000 |
1 |
The current number of client connections are %value% |
This metric should be consistent with the expected client load pattern for your system, that is, it should approximate the number of clients expected to be browsing newsgroups. Sustained high values could indicate an possible security breach (denial-of-service attack) in your system and should be further investigated. Check the NNTP server log files for any rejected connections. Use esd_logscan.pl to scan the server log files.
This metric category consists of news group related protocol server activity.
This metric indicates the rate at which newsgroups are being selected. Each group request also triggers a directory and database query. Thus, this metric indirectly indicates the load on your directory and database servers from the NNTP Inbound Server.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
Newsgroup selection by the client is a frequent activity. Sustained low values indicate that your news user population is very small or your news servers are not fully utilized. In this cased, if you are running several news server instances, some of them can be shut down.
This metric indicates the rate at which clients are listing news groups. The newsgroup listing is obtained from the directory and database servers using several successive queries. Thus, this metric indirectly indicates the load on your Oracle directory server and Oracle Collaboration Suite Databases from the NNTP Inbound Server.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
This is an infrequent client operation. In normal operation it must be near or at zero. Sustained high values for this metric indicate a possible security breach (denial of service attack) on your system and should be further investigated. Check the NNTP server log files for any rejected connections. Use esd_logscan.pl to scan the server log files.
This category contains metrics related to NNTP Inbound Server resource usage.
This metric is relevant only if Message Caching is enabled in the NNTP Inbound Server. This metric indicates the effectiveness of caching and should be between 0.5 and 1.0. Lower values usually mean that the caching is not useful for the client usage pattern for your system. A cache will be most effective when there are high traffic newsgroups with high levels of message retrieval.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
Message caching increases the memory usage on your host. A cache hit ratio does not usually justify the extra memory used by the server. If you see sustained values below 0.25 it is probably more efficient to turn off message caching in the NNTP Inbound Servers and reduce memory usage.
This metric indicates the number of threads which are in use in the multi-threaded NNTP Inbound Server processes on the host. Threads are destroyed if they remain idle for long (configurable) periods of time.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
The NNTP Inbound Server response category checks the NNTP Inbound Server process to see if the NNTP Inbound Server is running. Note that the NNTP Inbound Server response does not check the NNTP Inbound service. To see if a user can log into the NNTP Inbound Server refer to the NNTP Inbound Service response metrics.
This metric indiates whether at least one NNTP Server is running on the mid-tier host.
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 50-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 |
0 |
1 |
Failed to connect to NNTP server |
If the NNTP Inbound processes were intentionally stopped, they can be restarted. If the NNTP Inbound processes should be up but are not, then that is an indication they were not able to successfully initialize. Probable causes are an inability to contact or connect to either one of the mail information stores or the Oracle directory server. Perform the following checks.
Check that a process on the target is able to connect to and log into the Oracle directory server for the installation.
Verify that the Oracle Collaboration Suite Database is up and running and the connect string is correctly and accurately registered in the Oracle directory server.