eG Monitoring
 

Measures reported by MossSearchTest

SharePoint Server monitoring includes delivering comprehensive fault management and proactive alert notifications, checking for impending problems, triggering appropriate actions and gathering performance data for planning, analysis, and reporting. Monitoring SharePointServer can yield information in the following areas:

  • Overseeing overall system health
  • Detecting and predicting trends
  • Detecting errors
  • Ensuring good backups of your servers data
    Monitoring SharePoint server servers the purpose of avoiding service outages by detecting problems before they become critical. This test is used to provide counters that monitor the activities of the gatherer process when crawling local documents and can report IFilter and protocol handler errors

 The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Documents_filtered_rate Indicates the number of documents filtered per second. Documents/sec If this rate is decreasing over time, you should perform some troubleshooting to find out why your server is not filtering documents.

Look for memory issues, processor issues, network issues, or site hit frequency rules that slow the gatherer process.
Filtering_threads Indicates the total number of filtering threads in the system. Number  
Threads_accessing_network Indicates the number of threads waiting for a response from the filter process. Number If you don't see any activity, this counter equals the number of filtering threads; this number may indicate a network problem or unavailability of the server being crawled.
Active_queue_length Indicates the number of documents waiting for robot threads; Number If the value of this measure is not 0,then all threads should be filtered.
Admin_clients Indicates the number of currently connected administrative clients. Number  
Reason_to_back_off A code describing why the gatherer service went into back-off state. Number The values that this measure can take and the states they denote are available below:

0 - Up and Running.

1 - High system IO traffic.

2 - High notifications rate.

3 - Delayed recovery in progress.

4 - Due to user activity.

5 - Battery low.

6 - Memory low.

99 - Some internal reason.

During a back-off period, indexing is suspended. To manually back off the gatherer service, pause the search service. If the search service itself generates the back-off, an event will be recorded and the search service will be paused automatically. There is no automatic restart, so you must manually start the search service in order to end a back-off state. Note that there is little reason to start the search service until you've solved the problem that caused the back-off in the first place.
Threads_in_plug_ins Indicates the number of threads waiting for plug-ins to complete an operation. Number  
Delayed_documents Indicates the number of documents delayed due to site hit frequency rules. Number If you have a plethora of rules and this number is steadily increasing over time, consider relaxing or simplifying your site hit frequency rules.

A very high number may indicate a conflict in the rules that the gatherer cannot resolve or follow with efficiency.
Idle_threads Indicates the number of threads waiting for documents. Number  
Heartbeats_rate Indicates the number of heartbeats every 10 seconds. Heartbeats/sec