After reading this article you should have some good knowledge of system monitors and what an SM is capable of. From monitoring your system for hardware bottlenecks or service/application instability, SM should be your one-stop statistical resource gold mine. Becoming proficient using SM takes skill and a hands-on effort, only because so many processes can affect so many other different processes. For example, your ASP.NET application might have a slow request execution time because the amount of time the ASP.NET preprocessor is requiring of the processor to execute a request, may be beyond 70 percent of the processor's threshold frequently. Thus, you believe that the CPU is slow and should be upgraded, or the application should be hosted on a higher performance server.