Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Essentials edition. Server & Application Monitor (SAM) is also available in a standalone module.

Microsoft SharePoint Server 2016

This SAM application monitor template assesses the overall health and performance of Microsoft SharePoint Server 2016.

Prerequisites

WMI access to the SharePoint server.

Credentials

Windows Administrator on the SharePoint server.

To monitor a SharePoint server, you can also use Internet Information Service (IIS) Services and Counters, Windows Server 2003-2012 Services and Counters, and SQL Server 2005-2012 Performance templates.

Component monitors

Components without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find a threshold appropriate for your application.

Service: SharePoint Search Host Controller

This monitor returns CPU and memory usage of the SharePoint Search Host Controller service. This service performs host deployment and management for SharePoint search components.

Service: SharePoint Server Search 15

This monitor returns CPU and memory usage of the SharePoint Server Search 15 service. This service administers and crawls content from repositories.

Service: SharePoint Timer Service

This monitor returns CPU and memory usage of the SharePoint Timer service. This service sends notifications and performs scheduled tasks for SharePoint.

Service: SharePoint Tracing Service

This monitor returns CPU and memory usage of the SharePoint Tracing service. This service manages trace output.

Service: SharePoint User Code Host

This monitor returns CPU and memory usage of the SharePoint User Code Host service. This service executes user code in a sandbox.

Service: Document Conversions Launcher

This monitor returns CPU and memory usage of the Document Conversions Launcher service. This service schedules and initiates document conversions. When SharePoint Foundation passes a document conversion request to the document conversion launcher service, the service must call the appropriate document converter.

Service: Document Conversions Load Balancer

This monitor returns CPU and memory usage of the Document Conversions Load Balancer service. This service balances the document conversion requests from across the server farm. When it receives a converter request from SharePoint Foundation, the document conversion load balancer service must return a URI to the appropriate document conversion launcher service. SharePoint Foundation connects to the specified launcher via .NET remotely and requests the specified document be converted.

Current Requests

This component monitor returns the current number of requests, including those that are queued, currently executing, or waiting to be written to the client. Under the ASP.NET process model, when this counter exceeds the requestQueueLimit defined in the processModel configuration section, ASP.NET will begin rejecting requests.

Request Wait Time

This component monitor returns the time, in milliseconds, that the most recent request waited for processing. As the number of wait events increases, you may experience degraded page-rendering performance. This number should be as low as possible. If this value consistently grows, you should think about implementing additional web servers.

Requests Queued

This component monitor returns the number of requests waiting to be processed. SharePoint Foundation 2013 provides the building blocks for HTML pages that are rendered in the user browser over HTTP. This component monitor returns the number of requests waiting to be processed. If this counter shows hundreds or thousands of requests queued, you should implement additional web servers. The default maximum for this counter is 5,000. You can change this setting in the configuration file. This number should be as low as possible.

Requests Rejected

This component monitor returns the total number of requests not executed because of insufficient server resources. This represents the number of requests that return a 503 HTTP status code, indicating that the server is too busy. This value should be zero. If this value consistently grows, you should think about implementing additional web servers.

Worker Process Restarts

This component monitor returns the number of times a worker process has restarted. Restarts use a great deal of resources and therefore should be monitored closely. Restarts can be caused by various process settings, memory leaks, and access violations. It is recommended to closely monitor restarts to determine their cause, thus preventing them from occurring in the future. Any returned number above zero may indicate a problem.

Requests/Sec

This component monitor returns the number of requests executed per second. This represents the current throughput of the application. Under constant load, this number should remain within a certain range, barring other server work (such as garbage collection, cache cleanup thread, external server tools, and so on).

Cache API Trims

This component monitor returns the number of cache items that were removed due to a memory limit being hit, (i.e. they were trimmed). Ideally, this number should be very low or zero. Too many trims may indicate that you need to revisit your caching strategy or manually configure your cache memory limits.

Cache API Hit Ratio

This component monitor returns the cache hit-to-miss ratio when accessed through the external cache APIs. This counter does not track any use of the cache internally by ASP.NET. For read-only sites, the ratio should be 1. For read-write sites, the ratio may be lower.

Potential causes of a low hit ratio include the following:

  • You are using anonymous user caching and users are regularly requesting content that has not yet been cached.
  • You are using ASP.NET output caching for authenticated users and they have edit permissions on the pages they are viewing.
  • You have customized any of the VaryBy* parameters on a page or customized a cache profile.
  • You may have configured a parameter that prevents the pages in the site from being cached effectively.

Sql Query Executing time

This component monitor returns an average executing time of Sql queries. Returning value should be as low as possible.

Executing Sql Queries

This component monitor returns the number of current executing Sql queries.

Responded Page Requests Rate

This component monitor returns the number of requests responded in last second.

Executing Time/Page Request

This component monitor returns an average executing time (in ms) for responded requests in last seconds.

Current Page Requests

This component monitor returns the number of current requests in processing.

Rejected Page Requests Rate

This component monitor returns the number of rejecting requests in last second. Returning value should be as low as possible.

Incoming Page Requests Rate

This component monitor returns the number of incoming requests in last second.

Active Threads

This component monitor returns the number of threads currently executing in SharePoint code.