SharePoint Services (WSS) 3.0
This template assesses the overall health and performance of Windows SharePoint Services 3.0.
Prerequisites: WMI access to SharePoint server.
For more information, see “Requirements for Component Monitors and Templates that use WMI” in the Orion APM Administrator Guide.
Credentials: Windows Administrator on SharePoint server.
Note: For monitoring SharePoint server you can additionally use “Internet Information Service (IIS) Services and Counters”, “Windows Server 2003-2008 Services and Counters” and “SQL Server 2005-2008 Performance” templates.
Monitored Components
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. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415.
Internet Information Services
This component monitors only the service that provides Web connectivity through the Internet Information Services Manager.
SharePoint Services Search
This service provides support for constructing complex search queries through the SQL syntax. search in Windows SharePoint Services.
SharePoint Services Timer
This component monitor sends notifications and performs scheduled tasks for SharePoint.
SharePoint Services Tracing
This component monitor manages the trace output of the call stack. Administrators can specify the path used to store the trace log files. This log file may be used by applications that are built on top of Windows SharePoint Services 3.0.
ISAPI Connection Count
This component monitor returns the current number of extension requests that are simultaneously being processed by the web service.
ISAPI Request/Sec
This component monitor returns the rate at which ISAPI extension requests are simultaneously being processed by the web service.
ASP.NET 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.
