Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

SharePoint Server (MOSS) 2007

This template assess the overall health and performance of Microsoft Office SharePoint Server 2007.

Prerequisites

WMI access to SharePoint server.

Credentials

Windows Administrator on SharePoint server.

Component monitors

Click here for an overview about SAM application monitor templates and component monitors. SAM API Poller templates are also available.

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.

Document Conversions Launcher

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.

Document Conversions 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.

Single Sign-on

This component monitor provides the storage and mapping of credentials such as account names and passwords so that portal-based applications can retrieve information from third-party Enterprise Resource Planning (ERP) and Customer Relations Management (CRM) systems.

SharePoint Server Search

This is a server farm-wide service that responds to query requests from front-end Web servers or crawl items.

ASP.NET: Requests/sec

This component monitors 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). This value should be as low as possible.

ASP.NET: Worker Processes 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.

Search Indexer: Queries

This component monitor returns the number of search queries.

Search Gatherer: Crawls In Progress

This component monitor returns the number of crawls in progress. Unless an administrator has manually initiated a crawl, the value should match the number of content sources with crawls scheduled.

Search Gatherer: Document Add Rate

This component monitor returns the number of items indexed per second, per content source.

Search Gatherer: Error Rate

This component monitor returns the number of index errors per second and should be as low as possible.

Search Gatherer: Incremental Crawls

This component monitor returns the number of incremental crawls in progress. An incremental crawl indexes only items that have changed.

Search Gatherer: Processed Documents Rate

This component monitor returns the number of documents processed per second.

Search Gatherer: Retries

This component monitor returns the total number of times document access has been retried.

Search Gatherer: Waiting Documents

This component monitor returns the number of documents waiting to be processed.

Search Gatherer: Documents Filtered Rate

This component monitor returns the number of documents filtered per second.

Search Gatherer: Filtering Threads

This component monitor returns the number of threads that have retrieved content and are being filtered. If the number is high, it may indicate that resources on the index server are being bottlenecked. This number should be as low as possible.

Search Gatherer: Threads Accessing Network

This component monitor returns the number of threads in the gatherer process that have sent requests to a remote datastore and are either waiting for a response or processing a response. High values returned may indicate either a network bottleneck or that slow hosts may be connected to the index server.

Search Gatherer: Document Entries

This component monitor returns the number of document entries currently in memory.