Chapter 15: Monitoring SharePoint 2010
What’s In This Chapter?
- Improvements in diagnostic log management
- Using correlation IDs
- Using the logging database
If you’ve made it this far you’ve got SharePoint 2010 installed and running. You’ve created a web application or two and uploaded some content. You’ve probably configured some service applications and sent them off to do their work. SharePoint is doing its thing and life is good. You might be tempted to lean back in your chair and put your feet up, but your adventure is not finished. While SharePoint might be spinning like a top now, the day will come when there are problems. When that happens, you will need to know how to find out what’s troubling SharePoint so that you can fix it. A lot of work has been put into monitoring in SharePoint 2010. So much has been added that Monitoring has been given its own tab in Central Administration. SharePoint will report errors, but you need to know where to find them. This chapter will show you how to keep an eye on SharePoint, both in proactive and reactive ways so that you can keep your SharePoint servers in tip-top shape. This will enable you to fix SharePoint when it’s broken, as well as see where problem areas are before they become bad enough that your end users complain. Nobody likes that.
Unified Logging Service
We will start our journey toward SharePoint monitoring enlightenment with the Unified Logging Service (ULS). To the seasoned SharePoint administrator, the ULS logs are ...
