SharePoint 2013 monitoring

Size: px

Start display at page:

Download "SharePoint 2013 monitoring"

Amber Evans
5 years ago
Views:

1 SharePoint 2013 monitoring Objective Our goal is to monitor SharePoint 2013 in BMC TrueSight Operations Management and in BMC PATROL to detect failures, errors and performance issues. Solution Monitoring Studio KM for PATROL Our solution relies on Monitoring Studio KM for PATROL, which is a configurable module for BMC PATROL. Typically, a PATROL administrator will use Monitoring Studio KM s GUI to create the monitoring of anything which the administrator doesn t have a built-in KM for. The setup of the monitoring is stored in the PATROL Agent s configuration. More information on Monitoring Studio can be found here: Sentry has created a configuration for Monitoring Studio KM to monitor Microsoft SharePoint This article simply explains how to import this pre-built configuration and customize it to monitor your Microsoft SharePoint environment. Monitored components Database Objects will be dynamically created for each Microsoft SQL Server instance declared as a Content Database of the monitored SharePoint server. If the Microsoft SQL server is stopped or if there is an issue with the database server, these instances will go missing and a missing object alert will be triggered. The missing instances will be deleted after 5 polling cycles (this is a configurable setting). Event Log When Microsoft SharePoint encounters a problem, it reports it as an event in the Windows Event Log dedicated to Microsoft SharePoint Foundation. These events are constantly monitored by the solution and any Audit Failure, Error and Warning event related to SharePoint Foundation in the Windows Event Log will be reported in the console. Performance Metrics Many performance counters are monitored constantly to report the activity of Microsoft SharePoint and detect potential performance bottlenecks. Each performance counter is represented as a separate instance in the PATROL Console, grouped by the class of the corresponding Windows performance object. The performance metrics for objects such as.net CLR Memory, ASP.NET, Memory, MSSQL, Physical Disk and Virtual Server Web Service are all monitored. The template provides a set of predefined thresholds for some parameters. However they can be customized based on the customer s environment.

2 For example, below is the list of few parameters for which the thresholds are set: ASP.NET Requests Queued Trigger a WARNING if value is between 100 and 500; 1 time(s) in a row Trigger an ALARM if value is greater than 500; 1 time(s) in a row ASP.NET Requests Rejected Trigger a WARNING if value is between 1 and 5; 1 time(s) in a row Trigger an ALARM if value is greater than 5; 1 time(s) in a row Memory Available Mbytes Trigger an ALARM if value is lower than 1024; 1 time(s) in a row Trigger a WARNING if value is between 1024 and 2048; 1 time(s) in a row MSSQL SHAREPOINT:General Statistics User Connections Trigger a WARNING if value is greater than 100; 1 time(s) in a row MSSQL SHAREPOINT:Locks _Total Lock Wait Time (ms) Trigger a WARNING if value is greater than 1; 1 time(s) in a row MSSQL SHAREPOINT:Locks _Total Number of Deadlocks/sec Trigger a WARNING if value is greater than 1; 1 time(s) in a row Windows Processes Key performance metrics are constantly monitored for all of the Microsoft SharePoint processes. Each process is monitored independently and displayed as a separate object in the console. Monitored processes: hostcontrollerservice.exe lsass.exe mssearch.exe noderunner.exe Owstimer.exe SPUCHostService.exe SPUCWorkerProcess.exe SPUCWorkerProcessProxy.exe sqlservr.exe w3wp.exe wsstracing.exe For each of these processes, the following parameters are monitored: HandleCount PageFaultsPerSec PagefileBytes PrivateBytes

3 ProcessorTime ThreadCount VirtualBytes WorkingSet SharePoint Service Instances Monitors all the services instances of the entire SharePoint farm: - All the services that run under SharePoint will be discovered and an alert will be triggered if the service goes missing. - Also their status will be checked and alert will be triggered if the service is stopped. Sites Monitors the status of all the sites in Microsoft IIS: HTTP Availability HTTP Availability of the sites can be configured manually (see below) To configure the Web Request analysis from the PATROL Console, [right-click] on the application container under which you need to create the Web Request analysis [KM Commands] [New] [Web Request analysis]

5 Enter the URL of the site you wish to monitor and select the Http request type.

6 Enter the Object display name and the Object internal identifier and click on Finish to trigger a discovery.

7 Upon configuration the following parameters will be collected: Execution Time - A WARNING will be triggered if the value is more than 15 seconds and an ALARM will be triggered if the value is greater than 30 seconds HTTPStatusCode ServerConnectionState - An ALARM will be triggered if the server could not be reached Status - A WARNING will be triggered if the web page could not be reached Status - The status of all the sites under SharePoint is monitored by default. String search to alert on the sites that are stopped can be configured in addition. Web Application Monitor all the Application Pools in Microsoft IIS and their corresponding Windows processes: - Discovers all the Service Application Pools present and triggers a missing object alert when a Service Application Pool goes missing. - Also gets the list of Windows processes related to the Web Application Services.

8 Windows SharePoint Services The status of the services listed below is monitored by the solution. Each service is represented with a separate object in the console. The Status parameter reports the status of the service. This parameter will trigger an alarm if the service is stopped and a warning if the service is in an intermediate state (stop pending, paused, etc.). IIS ADMIN Service SharePoint Administration Service SharePoint Search Host Controller Service SharePoint Timer Service SharePoint Tracing Service World Wide Web Publishing Service Installation Prerequisites In order to setup the monitoring of Microsoft SharePoint 2013, you will need to make sure the following items are available, installed and properly configured: A fully functional BMC PATROL environment (optionally part of a larger BPPM environment), with a BMC PATROL Console A PATROL Agent on the SharePoint Server itself Monitoring Studio KM for PATROL, installed on the agent on the SharePoint Server itself Monitoring Studio KM is properly loaded on the agent and in the console The SharePoint2013_~.cfg installed in a folder on the SharePoint Server itself The PowerShell scripts from Scripts.zip extracted in a folder on the SharePoint Server itself

9 Procedure 1. From the PATROL Console, [right-click] on the main Monitoring Studio icon [KM Commands] [Configuration] [Import Configuration ]

10 2. Enter the path of the folder where you have stored the SharePoint2013.cfg file (this path is on the agent, on the SharePoint Server): 3. Select the SharePoint2013.cfg file in the list:

11 4. Monitoring Studio checks the content of the file. This process can take a few minutes (the configuration file is rather large). 5. Monitoring Studio is ready to import the configuration. Click [Finish] to start the import. 6. The import process can take a few minutes:

12 7. After the import process completes, Monitoring Studio KM starts creating the icons corresponding to the monitored objects in the PATROL Console and the icons are kept OFFLINE and the actual monitoring does not start until you enter a valid value for the %{SCRIPTPATH}

13 application constant:

8. To set the %{SCRIPTPATH} application constant value, [right-click] on the SharePoint 2013 icon in the PATROL Console [KM Commands] [Modify Application Constants ] 9.

14 8. To set the %{SCRIPTPATH} application constant value, [right-click] on the SharePoint 2013 icon in the PATROL Console [KM Commands] [Modify Application Constants ] 9. Next to the %{SCRIPTPATH} constant, enter the path of the folder where the PowerShell scripts are located and click [OK]. Also, the SharePoint username and password can be provided if you wish to execute the scripts and commands as a specific user. Alternate Installation Procedure Alternatively, PATROL administrators can use WPCONFIG.EXE, pconfig or PCM (PATROL Configuration Manager) to deploy the SharePoint2013.cfg configuration file. Once this is done, it is recommended to force a full discovery on the PATROL Agent to make sure Monitoring Studio KM takes into account the new configuration immediately (without waiting for the next discovery cycle, which occurs by default every hour). Post-installation tasks The different aspects of Microsoft SharePoint are grouped in containers/folders in Monitoring Studio. In order to identify the components that would need to be removed from the monitoring, you simply have to first browse the tree view to find the objects for which the Status parameter cannot be collected (it stays OFFLINE, while the rest of the monitoring is properly collected). Note: The powershell scripts uses the following SharePoint cmdlets: Get-SPDatabase

15 Get-SPServiceApplicationPool Get-SPServiceInstance Therefore the PATROL Agent default account should have access to execute these cmdlets or you should provide appropriate username and password to the application constants SPUSERNAME and SPPASSWORD. Thresholds Application container Monitored object Parameter Information Warning Alarm Database List of available Content Database Status =1 Cache Size (MB) Value N/A N/A Audit Failure MatchingEventCount >= 100 Event Log Warning MatchingEventCount >=1 Error MatchingEventCount >=1.NET CLR Memory _Global_ # Bytes in all heaps N/A N/A.NET CLR Memory.NET CLR Memory _Global_ % Time in GC N/A N/A.NET CLR Memory _Global_ Large Object Heap Size N/A N/A ASP.NET Application Restarts N/A N/A ASP.NET Request Execution Time N/A N/A ASP.NET ASP.NET Request Wait Time N/A N/A ASP.NET Requests Queued >500 Performance Memory MSSQL Physical Disk ASP.NET Requests Rejected 1-5 >5 ASP.NET Worker Process Restarts 1-5 >5 MemoryAvailable Mbytes 1 GB - 2 GB <1 GB Memory Pages/sec >200 Databases _Total Transactions/sec N/A N/A General Statistics User Connections N/A N/A Locks _Total Lock Wait Time (ms) >1000 Locks _Total Lock Waits/sec N/A N/A Locks _Total Number of Deadlocks/sec >1 SQL Statistics Batch Requests/sec >100 _Total % Disk Time >80 _Total Avg Disk Queue Length >2 _Total Disk Read Bytes/sec N/A N/A _Total Disk Write Bytes/sec N/A N/A

16 Web Service _Total Bytes Received/sec N/A N/A Virtual Server Web Service Web Service _Total Bytes Sent/sec N/A N/A Web Service _Total Current ISAPI Extension Request N/A N/A Web Service _Total ISAPI Extension Requests/sec N/A N/A Web Service-Current Connections N/A N/A All Windows processes related to SharePointChildCount N/A N/A Count =0 HandleCount N/A N/A PageFaultsPerSec N/A N/A Processes PagefileBytes N/A N/A PrivateBytes N/A N/A ProcessorTime >=90 ThreadCount N/A N/A VirtualBytes N/A N/A WorkingSet N/A N/A SharePoint List of all SharePoint Services Service Instances Status!=Online Sites Http Availability ExecutionTime >=30 List of all sites in the IIS Status N/A N/A All Web Application Pools Status =1 Web Application All Web Application Service Instances PID Status =1

HPE IMC APM SQL Server Application Monitor Configuration Examples

HPE IMC APM SQL Server Application Monitor Configuration Examples Part number: 5200-1353 Software version: IMC APM 7.2 (E0401) Document version: 1 The information in this document is subject to change