SharePoint Server 2010
This template assesses the overall health and performance of Microsoft SharePoint Server 2010.
WMI access to SharePoint server.
Windows Administrator on SharePoint server.
Click here for an overview about SAM application monitor templates and 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 2010 Timer
This component monitor sends notifications and performs scheduled tasks for SharePoint.
Service: SharePoint 2010 Tracing
This component monitor manages trace output.
Service: SharePoint 2010 User Code Host
This component monitor executes user code in a sandbox.
Service: SharePoint Foundation Search V4
This service provides full-text indexing and search to SharePoint user and help content.
Service: SharePoint Server Search 14
SharePoint Server Search 14 provides enhanced full-text indexing and search capabilities.
Service: Document Conversions Launcher
This component launches the Microsoft SharePoint Server 2010 Document Conversions Services. 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 component launches the Microsoft SharePoint Server 2010 Document Conversions Services Load Balancer. 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.
Cache API Trims
This component monitor returns the number of cache items that have been 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
SharePoint Foundation 2010 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.
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.
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.
This component monitor returns t 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