An Oracle Collaboration Suite Database (mailstore) target contains message and mail queue management information. The Oracle Collaboration Suite Database contains a single copy of an e-mail message with multiple instance records of that message, depending upon the number of recipients and the number of times it was copied into different folders.
The Message Queue category contains metrics about mail messages in a mail store that are queued to be processed by a mail server. Mail servers which process queued messages are the SMTP Outbound, List, and NNTP Outbound servers.
The following diagnostic scripts can be used to get more details about the status of queues:
esd_mail_queue.sql: Use this script to examine the contents of a queue or all queues. Important information, such as sender of the message, sent date, and subject, about each message in a queue is listed.
esd_queue_examine.sql: Use this script to list the top 5 most frequently found subjects, senders, and recipients of messages in the submit queue.
See Appendix D, "Oracle Mail Command-Line Reference" in Oracle Mail Adminstrator's Guide for more information these scripts.
This metric is a gauge that measures the number of messages captured by all SMTP and list server processes for this Oracle Collaboration Suite Database (mailstore) that need to have archive message copies built and sent.
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 44-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 |
> |
750 |
1000 |
1 |
The length of archive queue is %value% |
A relatively low and constant number is desirable for this metric. If the number is trending up, then there is probably not enough SMTP Outbound processing resoures applied to Archive Queue Processing. A spike in the queue could indicate an unusual burst of archivable traffic but, if the spike does not start to return, one of the target archive repositories might not be available.
If SMTP Outbound processes are running and the queue is still growing, check the following:
Consider creating a separate and dedicated SMTP Outbound instance to processing the archive queue.
Check the resources available to the Oracle Collaboration Suite Database host to ensure that host has sufficient memory and CPU.
Check the resources available to the Oracle Collaboration Suite host running the SMTP Outbound process(es) to ensure that host has sufficient memory and CPU.
Consider increasing the concurrency of the SMTP Outbound process(es) that process the archive queue.
Check the archive policy e-mail addresses or relay hosts and port numbers to ensure they are not rejecting connections and are capable of receiving messages.
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 44-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 |
> |
750 |
1000 |
1 |
The length of collection queue is %value% |
This metric is a gauge that measures the number of messages that are in the list server queue. The messages in this queue are sent to mailing lists and have to be processed by the list 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 44-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 |
> |
750 |
1000 |
1 |
The length of list queue is %value% |
This metric is a gauge that measures the number of messages that are in the local delivery queue. The messages in this queue have to be processed by SMTP Outbound or list 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 44-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 |
> |
750 |
1000 |
1 |
The length of local queue is %value% |
This metric is a gauge that measures the number of messages that are in the NNTP Outbound queue. The messages in this queue have to be fed to other news servers and have to be processed by the NNTP Outbound 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 44-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 10 Minutes |
After Every Sample |
> |
750 |
1000 |
1 |
The length of NNTP queue is %value% |
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 44-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 10 Minutes |
After Every Sample |
> |
750 |
1000 |
1 |
The length of prune queue is %value% |
This metric is a gauge that measures the number of messages that are in the relay queue. The messages in this queue have to be processed by the SMTP Outbound or list 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 44-7 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 |
> |
750 |
1000 |
1 |
The length of relay queue is %value% |
This metric is a gauge that measures the number of messages that are in the submit queue. The messages in this queue have to be processed by the SMTP Outbound 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 44-8 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 |
> |
750 |
1000 |
1 |
The length of submit queue is %value% |
This metric is a gauge that measures the number of messages which are currently being processed by the various Oracle Mail servers, including SMTP Outbound, list server, and NNTP Outbound.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
This metric is a gauge that measures the number of messages that are in the local delivery queue but could not be delivered due to the mailbox being full or some other reason. The messages in this queue will be retried for delivery by the SMTP Outbound 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 metric is a gauge that measures the number of messages that are in the relay queue but could not be delivered due to the relay SMTP server being unavailable or some other reason. The messages in this queue will be retried for delivery by the SMTP Outbound server.
The following table shows how often the metric's value is collected.
| Target Version | Evaluation and Collection Frequency |
|---|---|
| All Versions | Every 10 minutes |
The Mailstore Response category contains metrics that provide information about the Up/Down status of an instance of the Oracle Collaboration Suite Database (mailstore).
The Response Status metric indicates whether or not the Oracle Collaboration Suite Database is available to use as a mail store. A value of one (1) means the Oracle Collaboration Suite Database is up and running along with the database listener (the Oracle Listener). A value of zero means it is not 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 44-9 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 |
= |
Not Defiend |
0 |
1 |
Failed to connect to the database |