Monitor a SharePoint environment

The first few steps after implementation are often the most critical. A sudden uptick in user
adoption shortly arrives and may expose any design inconsistencies not discovered during
performance testing. Previously defined service level agreements (SLAs) with the business
may also be in effect, restricting the times that the system can be down for maintenance.
Ensuring reliability and performance levels during this period is a key requirement for
user adoption of the new platform. Effective administration and monitoring of the Share-
Point environment can capture events, addressing any misconfigurations or design shortfalls
before they affect user adoption.

We need to understand following definition and configuration requirements to monitor SharePoint Environment:

 Summary:

  • SLAs define the service metrics used within a SharePoint farm; these agreements include definitions such as “downtime,” “scheduled downtime,” and “monthly uptime percentage,” which describe the goals of monitoring within the farm.
  • SharePoint farms provide performance counters that enable you to monitor the farm at three distinct levels: server, service application, and site/site collection.
  • The Get-SPLogEvent cmdlet enables you to view trace log events (ULS logs) by level, area, category, event ID, process, or message text.
  • System Center Management Pack for SharePoint 2013 works in conjunction with System Center 2012 Operations Manager to monitor both SharePoint Server 2013 and Project Server 2013 farms.
  • Performance Monitor not only monitors Windows Server 2012 performance counters but also SharePoint counters for subsystems such as search, InfoPath Forms Services, and others.
  • Page performance monitoring is dependent on the counters presented by the ASP.NET output cache, BLOB cache, object cache, and the Distributed Cache Service.
  • The usage and health data collection service allows for the capture and centralization of SharePoint performance metrics within the logging database.