Sunday, August 9, 2020

Search health reports

The search system in SharePoint Server 2013 provides two main kinds of health reports, query health reports and crawl health reports.

In this article

Query health reports

Crawl health reports

Query health reports

The following reports about query performance are available:

Query Health Report

Description

Trend (Query Latency Trend)

For a specified time interval, shows the query latency (in milliseconds) by percentile. For example, five percent of all queries had lower latency than the latency indicated by the fifth percentile line in the graph.

The graph includes an overlay of query rate during the specified time interval, where query rate is the number of queries per minute for which the query object model (OM) returned results.

The graph also includes an overlay of the crawl rate and the partial update rate for analytics.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client type

  • Result page (search results page), which only shows if verbose logging is enabled.

By default, the graph displays data for all result pages in the Search service application.

Overall (Overall Query Latency)

For a specified time interval, shows the query rate (number of queries per minute) with an overlay of query latency in milliseconds.

Shows the query latency in each of the following areas:

  • Object model. This is the time it takes to communicate between the web server and the back-end.

  • Backend. This is the time it takes to transform the query, perform index look up, process results (such as removing duplicates), and return results to the object model.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client Type

  • Result page (search results page), which only shows if verbose logging is enabled.

By default, the graph shows data for all result pages in the Search service application.

Main Flow (Default SharePoint Flow Query Latency)

For a specified time interval, shows the query latency (in milliseconds) in the main flow for query and result processing. This indicates how fast the system processes a query and returns results to the web server. The graph shows the query latency for:

  • Query rule condition matching

  • Query transformation

  • Query routing

  • Result mixing

  • Layout selection

  • Query logging

  • Other

The graph includes an overlay of query rate during the specified time interval.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client Type

Federation (Federation Query Latency)

For a specified time interval, shows the query latency in milliseconds for all result source types.

By default, the graph shows data for all result pages in the Search service application.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client type

  • Result page (search results page), which only shows if verbose logging is enabled.

  • Source type (result source type):

  • Best Bet Provider

  • Exchange Search Provider

  • Local People Provider

  • Local SharePoint Provider

  • OpenSearch Provider

  • Personal Favorites Provider

  • Remote People Provider

SharePoint Search Provider (Local SharePoint Search Flow Query Latency)

For a specified time interval, shows the query latency (in milliseconds) for all queries that are processed by the local SharePoint search provider. The graph shows the query latency for:

  • Keyword parsing

  • Linguistics

  • Recommendations Security Trimming

  • Security token construction

  • Index lookup

  • Result type processing

  • Custom security trimming

  • Summary generation

  • Other

The graph includes an overlay of query rate during the specified time interval.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client type

People Search Provider (People Search Flow Query Latency)

For a specified time interval, shows the query latency (in milliseconds) for all queries that are processed by the local people search provider. The graph shows the query latency in each of the following areas:

  • Keyword parsing

  • Linguistics

  • People pre-processing

  • Security token construction

  • Index lookup

  • Result type processing

  • Custom security trimming

  • Summary generation

  • Other

The graph includes an overlay of query rate during the specified time interval.

You can filter this report by:

  • Start date/time

  • End date/time

  • Client type

Index Engine (Index Engine Query Latency

For a specified time interval, shows the query latency in milliseconds for each index server that you filter on. By default, the graph shows data for all result pages in the Search service application. You can filter this report by:

  • Start date/time

  • End date/time

  • Index server (a computer that hosts at least one index partition)

  • Result page (search results page), which only shows if verbose logging is enabled.

The graph includes an overlay of the index lookup time for the specified time interval in the past. Index lookup time is the average amount of time during a given minute that it took the index engine to return results. The index lookup time applies only to queries for which the index engine returned results.

Top of Page

Crawl health reports

The following reports about crawl health are available:

Crawl Report

Description

Crawl Rate

For a specified time interval, shows a graph and a summary of the following:

  • Number of content items crawled per minute. This includes:

  • Total content items

  • Modified items. These are content items that were changed and re-crawled.

  • Not modified items. These are content items that were not changed and were not crawled.

  • Security items. These are content items for which the security attributes were changed.

  • Deleted items. These are content items that were deleted from the content source and which must also be deleted from the index.

  • Average number of other crawl actions that were performed per minute. This includes:

  • Retries (crawl retries)

  • Errors (crawl errors)

You can filter this report by:

  • Start date/time

  • End date/time

  • Content sources (for example, Local SharePoint sites)

  • Machine

Crawl Latency

For a specified time, shows a graph of the number of items that form the crawl load, for each of the following:

  • In Crawler Queue

  • Waiting to submit to content processing

  • Submitted to content processing

  • Waiting to Commit (SQL)

You can filter this report by machine only.

For a specified time interval, also shows a graph and a summary of the crawl latency; the amount of time in milliseconds that each content item is in each of the following subsystems in the feeding pipeline:

  • Crawler

  • Protocol handler (PH)

  • Repository

  • SQL Time

You can filter this report by:

  • Start date/time

  • End date/time

  • Content source (for example, Local SharePoint sites)

  • Machine

Crawl Queue

For a specified time interval, shows the number of items in the following two crawl queues:

  • Links to process. This is the number of uncrawled URLs that are queued to be crawled.

  • Transactions queued. This is the number of crawled URLs that arequeued to be processed in the crawl pipeline.

You can filter this report by start date/time and end date/time.

Crawl Freshness

For a specified time interval, shows the freshness of the content that was being indexed by the search system. The last modified time stamp of each document is compared with the time specified in the graph. You can view the freshness of the content as follows:

  • Less than 1 month ago

  • Less than 1 week ago

  • Less than 1 day ago

  • Less than 4 hours ago

Content Processing Activity

For a specified time interval, shows the amount of time that was spent in content processing for:

  • Content sources

  • Machines

  • Content processing components

  • Content processing activity

The graph shows the amount of time that was spent in various content processing activities, such as:

  • Linguistics processing

  • Document parsing

  • Document summary generation

  • Indexing

You can filter this report by:

  • Start date/time

  • End date/time

  • Content source

  • Machine

  • Content processing component name

  • Processing activity

CPU And Memory Load

For a specified time interval, shows the percentage of CPU used, the memory use in megabytes and the system overview for these processes:

  • MSSDmn

  • MSSearch

  • NodeRunner

  • Timer

You can filter this report by:

  • Machine

  • Start date/time

  • End date/time

Continuous Crawl

For a specified time interval, shows the time (in milliseconds) that the processes took with an overlay of discovery time (in minutes) for:

  • Time In Links Table

  • Time In Queue Table

  • Crawler Time

  • PH (Protocol Handler) Time

  • Repository Time

  • Content Pipeline Time

  • SQL Time

You can filter this report by:

  • Content sources

  • Start date/time

  • End date/time

For more information, see View search diagnostics on TechNet.

Top of Page

No comments:

Post a Comment