What performance counters are used to monitor current and queued operations by indexing service.

Monitoring performance counters will enable Enterprise Vault (EV) Support and Administrators to verify the progress of indexing service operations. 

 

A number of EVIndexVolumesProcessor.exe performance counters are available to EV Administrators for monitoring current and queued indexing service operations: 

 

1. Number of indexing agents 

Number of index volumes processed by enterprise vault indexing service at a given time. Maximum number of index volumes processed by indexing service at a given time is 30.

 

2. Synchronization queue count

Synchronization queue count will contain the number of index volumes requiring any pending work discovered by storage via indexing admin service, Search or StoragePendingWorkDiscovery. 

 

        Synchronization Queue count is also updated by following processes:

          i. Storage via the Index Admin Service when items are added updated or deleted in an EV archive.

          ii. Search, if an index volume is searched for which the metadata in the directory database indicates that there is work pending.
 

        StoragePendingWorkDiscovery checks for any pending indexing work, EVIndexVolumesProcessor is then notified about any pending work by updating synchronization queue count. 

 

        StoragePendingWorkDiscovery runs as part of synchronization process, by default synchronization runs are configured as following:

          i. Startup of indexing service

          ii. 1 hourly synchronization check

          iii. 6 hourly synchronization check

          iv. 10 hourly synchronization check

 

3. Subtask queue count

The number of subtask work items pending execution. This is a processing queue holding subtask work item identifiers for particular subtasks (i.e. synchronize or rebuild) which are waiting to be processed by IVP (EVIndexVolumesProcessor).

 

4. Work item queue count

This is a prioritized queue holding indexing work items whilst they are not actively being processed by an index volume agent. 

Work items prioritization is based on volume and job type and is achieved using internal queues allowing higher priority work items to move faster through the queue than those of lower priority. 

 

5. Work item throttling count

Number of index volumes currently being throttled. Throttling occurs when Enterprise Vault times out while waiting for the 64-bit indexing engine to index data for an index volume. Index volume is again re queued in Work item queue for processing.

 

6. Task queue count

A single task queue exists for every Index Administration Task (and so normally will only be 1) but in building blocks environments can be higher (indicating that an index server is servicing the work of multiple Index Administration Tasks).  This queue is essential for a building blocks environment in which one indexing service may become responsible for processing the subtasks of failed over indexing service. When Index Administration Tasks from two indexing services are running simultaneously then task queue count will be incremented to ‘2’.