16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 251<br />

Maintaining a Problem History<br />

You should design the monitoring solution to provide an accurate history of events<br />

<strong>and</strong> problems. For example, if the network management <strong>and</strong> monitoring system logs<br />

events in a st<strong>and</strong>ard format, the IIS-related entries can be periodically extracted, compiled,<br />

<strong>and</strong> archived in a central location for periodic review later. These extracted logs<br />

provide critical trend data that can be used to perform the following tasks:<br />

■ Identify recurring problems.<br />

■ Support capacity planning.<br />

■ Provide summary information about reliability <strong>and</strong> availability.<br />

You should consider maintaining an issue log to track problems <strong>and</strong> solutions<br />

for future reference. If a problem recurs, future users can see how it was previously<br />

resolved.<br />

Maintaining a Written Plan<br />

You need a written plan that provides timely, accurate, consistent, <strong>and</strong> reusable<br />

responses for every failure, event, or problem. Executing a consistent plan for<br />

addressing recurring events helps avoid wasting time, resources, <strong>and</strong> money.<br />

Using Effective Notification Techniques<br />

Actively capturing real-time event information is useful only if the responsible parties<br />

are notified to implement the action plan. Event notification accomplishes the<br />

following four important goals:<br />

■ It notifies the parties responsible for fixing the problem.<br />

■ It notifies the parties responsible for administration of the system.<br />

■ It notifies the parties affected by the event. Users do not need to know the<br />

details of the problem, but they need to know if there is an interruption, or<br />

anticipated interruption, <strong>and</strong> when the problem will be resolved.<br />

■ It notifies each party to take appropriate action.<br />

After you have captured an event <strong>and</strong> have notified the responsible people,<br />

you should do the following:<br />

■ Minimize the impact of the problem.<br />

■ Perform a root-cause analysis to determine the exact nature of the problem.<br />

■ Correct the problem.<br />

■ Create a plan for providing a long-term solution <strong>and</strong> a reusable action plan<br />

should the event recur.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!