Performance counters
IBM® Content Collector provides a variety of performance counters.
The following counters are useful for regular system monitoring.
Some of these counters are monitored by the Content Collector system dashboard.
- Accessed Entities (monitored by the dashboard)
- Accessed Entities/sec (monitored by the dashboard)
- Documents Created (monitored by the dashboard)
- Documents Created/sec (monitored by the dashboard)
- Duplicate Documents (if archiving to FileNet® P8)
- Additional instances (if archiving to IBM Content Manager)
- Run Count
- Searched Locations
Table 1 lists the
available performance counters to monitor IBM Content Collector.
| Counter name | Performance object | Counter description | Recorded on |
|---|---|---|---|
| Accessed Entities | CTMS Collector | Number of items accessed by the collector. If no errors have occurred, this will be equal to the submitted items plus the skipped items. | Primary node |
| Accessed Entities/sec | CTMS Collector | Number of items accessed per second. | Primary node |
| Connector Failures | CTMS Connector Health | Number of times a connector failed. If you select the instance _Total for this counter, the counter shows the total value for all connectors. | Any node |
| Container Count | CTMS Instanceless Core | Number of containers that the node is processing. A container is an object that provides information about the location of the entities to be processed, for example, the location of a mailbox. | Any node |
| Documents Created | CTMS Target | Number of documents created in the repository. | Any node |
| Documents Created/sec | CTMS Target | Number of documents created in the repository per second. | Any node |
| Entity Errors | CTMS Collector | Number of items that were skipped by the source connector due to errors. | Primary node |
| Entity Errors/sec | CTMS Collector | Number of items that were skipped per second due to errors. | Primary node |
| Forwarded Items | CTMS Core | Number of items that were forwarded to a secondary task route service. | Primary node |
| Forwarded Items/sec | CTMS Core | Number of items that were forwarded to a secondary task route service per second. | Primary node |
| Forwarding Errors | CTMS Core | Number of errors that occurred while attempting to forward to secondary nodes. | Primary node |
| Forwarding Errors/sec | CTMS Core | Number of errors that occurred per second while attempting to forward to secondary nodes. | Primary node |
| Forwarding Threads | CTMS Instanceless Core | Number of threads that are currently forwarding work to secondary nodes.1 | Primary node |
| Item Backlog | CTMS Instanceless Core | Number of submitted items for which processing has not yet started. | Any node |
| Location Errors | CTMS Collector | Number of locations that were skipped due to errors. | Primary node |
| Location Errors/sec | CTMS Collector | Number of locations that were skipped per second due to errors. | Primary node |
| Rejected Items | CTMS Core | Number of items that were rejected because they were already being processed at submission time. | Any node |
| Rejected Items/sec | CTMS Core | Number of items that were rejected per second because they were already being processed at submission time. | Any node |
| Releasing Threads | CTMS Instanceless Core | Number of threads that are currently handling release notifications from secondary nodes. Secondary nodes periodically inform the primary node of the work they have completed.1 | Primary node |
| Restart Count | CTMS Connector Health | Number of times a connector was restarted. If you select the instance _Total for this counter, the counter shows the total value for all connectors. | Any node |
| Run Count | CTMS Collector | Number of times the collector has run. | Primary node |
| Runs/sec | CTMS Collector | Number of times the collector has run per second. | Primary node |
| Searched Locations | CTMS Collector | Number of locations searched. | Primary node |
| Searched Locations/sec | CTMS Collector | Number of locations searched per second. | Primary node |
| Secondary Nodes | CTMS Instanceless Core | Number of secondary nodes. | Any node |
| Submitted Items | CTMS Core | Number of items that were submitted to the task route service. | Any node |
| Submitted Items/sec | CTMS Core | Number of items that were submitted to the task route service per second. | Any node |
| Threads Handling Connections | CTMS Instanceless Core | Number of threads that are currently handling connections to a collector or another node. | Any node |
| Threads Handling Queue | CTMS Instanceless Core | Number of threads that are currently processing the entity queue. When a thread handles a submission from a collector or another node it checks whether any other thread already processes the entity queue. If not, the thread takes on this task: it pulls items off the queue and feeds them to available idle threads, and also processes entities itself. Usually, the value of this counter is one. | Any node |
| Threads Processing Entities | CTMS Instanceless Core | Number of threads that are currently processing entities according to the appropriate task route. | Any node |
| Threads Routing to Primary | CTMS Instanceless Core | Number of threads that are currently submitting distributable entities that were found in the assigned collection source to the primary node for further processing. A distributable entity, for example, is an email in a mailbox. A nondistributable entity, for example, is an email in a PST file because processing of local files is tied to one node. | Secondary node |
Table 2 lists
the available performance counters to monitor information about the IBM Content Manager connector.
| Counter name | Performance object | Counter description |
|---|---|---|
| Additional Instances | CMV8 Connector | Number of additional instances that have been recorded. For example, if two people receive the same email, both have an instance of the email. For the first instance to be archived, the Documents Created counter is incremented. For any additional instances, the Additional Instances counter is incremented. |
| Average Attachment Size | CMV8 Connector | Average size of attachments archived since the service was started. |
| Average Document Size | CMV8 Connector | Average size of documents archived since the service was started. |
| Average Email Size | CMV8 Connector | Average size of email messages archived since the service was started. |
| Instance Uniqueness Constraint Violations | CMV8 Connector | If the record of an additional instance cannot be created because one of the attribute values of the instance violate a uniqueness constraint, then this counter is incremented. |
| JVM Free Memory | CMV8 Connector JVM | Portion of total memory that is not in use. |
| JVM Max Memory | CMV8 Connector JVM | Maximum memory that the JVM will use. |
| JVM Total Memory | CMV8 Connector JVM | Amount of memory that the JVM currently uses. |
| JVM Used Objects | CMV8 Connector JVM | Number of objects on the heap. This counter is updated if memory dumps have been enabled or if the environment variable IBM_CTMS_CMV8_SHOW_OBJECT_COUNT has been set. |
| Percentage Duplicate Documents | CMV8 Connector | Percentage of documents that are duplicates of existing documents. |
Table 3 lists
the available performance counters to monitor information about the FileNet P8 connector.
| Counter name | Performance object | Counter description |
|---|---|---|
| Duplicate Documents | P8 Connector | Number of duplicate documents that the P8 Create Document task detects. |
| Duplicate E-mail Instances | P8 Connector | Number of duplicate email instances that the P8 Create Email Instance task detects. |
| E-mail Instances Created | P8 Connector | Number of email instances that the P8 Create Email Instance task creates. |
| Number of Maintenance Task Invocations | P8 Connector Consolidation | Number of times that the maintenance task is invoked by the IBM FileNet P8 Connector. |
| Number of XITs Updated | P8 Connector Consolidation | Number of XITs that are updated by the IBM FileNet P8 Connector maintenance task. |
| Rate of Duplicate Documents | P8 Connector | Rate of duplicate documents that are detected by the P8 Create Document task (documents/sec). |
| Rate of Duplicate Email Instances | P8 Connector | Rate of duplicate email instances that are detected by the P8 Create Email Instance task (EIs/sec). |
| Rate of Email Instances Created | P8 Connector | Rate of email instances that are created by the P8 Create Email Instance task (EIs/sec). |
| Rate of XITs Updated | P8 Connector Consolidation | Rate of XITs that are updated by the IBM FileNet P8 Connector maintenance task (XITs/sec). |
| Sampled Average Attachment Size | P8 Connector | Size of archived attachments in bytes, averaged over the number of attachments that are archived in 1 second (bytes/sec). |
| Sampled Average Email Body Size | P8 Connector | Size of archived email bodies in bytes, averaged over all email documents that are archived in 1 second (bytes/sec). |
| Sampled Percentage of Duplicate Email Documents | P8 Connector | Percentage of duplicate email documents that are detected and archived into FileNet P8 Content Engine, averaged over all emails that are archived in 1 second (% duplicates/sec). |
| Sampled Average XIT Content Size | P8 Connector Consolidation | Size of the XIT content that is added to FileNet P8 Content Engine in bytes, averaged over all XITs that are archived in 1 second (bytes/sec). |
1 Each of these threads is also handling a
connection.