Skip to main content

SharePoint 2013 Search Diagnostics

Image
By
SharePoint Search 2013 infrastructure totally changed and now in 2013 provides the great OOB tools that help to troubleshoot the problem more easily. Monitor the crawl and query rates and latency and generate the reports.

So the following are the some of the great tools that exist in the SharePoint 2010 Fast Infrastructure but 2013 it adds more options in crawl logs also display the crawl and query health reports in form of charts.

Crawl logs: The crawl logs basic first level entry where the SharePoint administrator checks the crawl status. So the following are the options that added in the existing crawl logs that gives the more help in terms of analysis the & check the performance of the crawler.
  • Content Source (added 1, 7 and 30 day duration trend)
  • URL View (Added new link remove from index)
  • History( added new column Latency and load)
Content source

URL View
History View
Crawl Health Report: Display the health report card of the crawler the report generate in the forms of graph. The following are reports that displays. Apply the filter based on the content source and the crawl component, with the help of the report card we can analysis and check the health of the crawler and take the decision during the peak time what would be output of the crawler and is required to add more crawler to crawl the content.

  • Crawl Rate (dps): Crawl rate per type that includes (Modified, not modified, security only, deleted, retry and error ) and crawl rate per content source (document per second).
  • Crawl Latency: Crawl load (In crawler queue, Waiting for content Plugin, Submitting to CTS, Waiting for commit(SQL) ) and latency time (Repository, Protocol handler, crawler, CTS and SQL)
  • Crawl Freshness: Shows the content freshness that includes aggregate freshness and pre day & mins. 
  • CPU & Memory Load : Total CPU usage and memory usage also more details chart about the memory usage by Process(MSSDMN, MSSearch,NodeRunner andTimer) and CPU usage by process (MSSDMN, MSSearch,NodeRunner andTimer)
  • Content Processing Activity(Processing items): content process activity taken by each process (WordBreaker, term extractor ,Security insert, Search Analysis, Property mapping, profiler manager extractor, phonenumber normalization, OOTBextraction, noIndex, MetadataExtractor, Language Detector, indexing, document summary ect)
  • Crawl Queue(items): shows the items are queue (Links to Process and Transaction queued)
  • Continues Crawl(Tiime/Discovery time) : Display the performance of the continues crawl (Links Table, crawler, protocol handler, repository, content pipeline,SQL and Queue table. 

Query Health Report: Display the health report card of the query site. This report would help the take decision on the query time. How much time would take to process the query?

  • Trend(Query latency m.sec/items per second): display the crawl rate and analytics update rates   Overall : Show the overall reports 
  • Main Flow(Query latency m.sec/items per second): Trend of the query  in terms of (Query rule condition matching, Query routing, layout selection, query logging, query transformation, result mixing and other) 
  • Federation: That includes (Best bet provider, local SharePoint Provider, personal favorites providers, Exchange search provider, open search provider, remote search provider and local people provider)
  • SharePoint Search Provider: That’s include (keyword parsing, linguistics, Recommendation security trimming ,security token construction ,index lookup ,Result type processing, custom security trimming, summary generation and other)
  • People Search Provider :That’s include (keyword parsing, linguistics, Recommendation security trimming ,security token construction ,index lookup ,Result type processing, custom security trimming, summary generation and other)
  • Index Engine: latency by the content source (Index lookup)



Usage Reports: The usage reports shows the usage reports as well as the search reports that included the list of following csv file generating by the timer jobs that helps the Search analyst to take the decision and check the trend of the keyword and query that mostly search by the users. Following are the list of the reports. 
  • Number of query 
  • Top queries by day 
  • Top queries by month 
  • Abandoned queries by day 
  • Abandoned queries by month 
  • No Result queries by day 
  • No Result queries by month 
  • Query rule usage by day 
  • Query rues usage by month
Developer Dashboard: In SharePoint 2013 developer dashboard comes with more options and it has more option it trace each and every request like the fiddler. The good news is that now not required to physically check the ULS logs now the ULS logs option there.
  • Server Info
  • Scopes
  • SQL
  • SPRequest
  • Asserts 
  • Service Calls
  • ULS
  • Cache Calls
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more