I would like to monitor the disk performance on disk queue lenght, I would like to know what value for disk queue lenght should be a abnormal status ? whether over 5 can determine this is high ? Pls advice. Thx !!

Hi, Import the Base OS Management Pack: http://www.microsoft.com/en-us/download/details.aspx?id=9296 Introduction to the System Center Monitoring Pack for the Windows Server Operating System http://technet.microsoft.com/en-us/library/dd262074.aspx Monitoring Logical and Physical Disks: http://technet.microsoft.com/en-us/library/dd262028.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Everyone, including MSFT, will have "general" guidelines about disk performance. These are just what they are "guidelines" and not necessarily for your environment. For example, in the past for older versions of Exchange and maybe even 2010, avg disk reads per sec and writes per sec were to be >< .05. Well in our beefy Exchange environment, back in the day, we couldn't get those low numbers, so we set up collection rules, figured out what our "normal" was and adjusted monitoring for our "average". Same thing goes for processor, etc. These are good averages, but depending on your environment and the resources you have you may never MEET them, so you will get alerted all the time. What you need to do is find out what the LOB requirements are for their application, measure the various performance counters, and find out what their application is performing at right now, give them that information, and if they want to meet their SLA, then they will have to build a better system, otherwise, build your monitoring around your collected data. Does this make sense? Disk queue length is an important counter, but there are various underlining issues that can cause disk to queue. You may have very fast disk and or a lot of iops dedicated for a lun on san storage, but your proc or memory isn't enough and or your page file is not configured correctly. Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

Hi, Import the Base OS Management Pack: http://www.microsoft.com/en-us/download/details.aspx?id=9296 Introduction to the System Center Monitoring Pack for the Windows Server Operating System http://technet.microsoft.com/en-us/library/dd262074.aspx Monitoring Logical and Physical Disks: http://technet.microsoft.com/en-us/library/dd262028.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Everyone, including MSFT, will have "general" guidelines about disk performance. These are just what they are "guidelines" and not necessarily for your environment. For example, in the past for older versions of Exchange and maybe even 2010, avg disk reads per sec and writes per sec were to be >< .05. Well in our beefy Exchange environment, back in the day, we couldn't get those low numbers, so we set up collection rules, figured out what our "normal" was and adjusted monitoring for our "average". Same thing goes for processor, etc. These are good averages, but depending on your environment and the resources you have you may never MEET them, so you will get alerted all the time. What you need to do is find out what the LOB requirements are for their application, measure the various performance counters, and find out what their application is performing at right now, give them that information, and if they want to meet their SLA, then they will have to build a better system, otherwise, build your monitoring around your collected data. Does this make sense? Disk queue length is an important counter, but there are various underlining issues that can cause disk to queue. You may have very fast disk and or a lot of iops dedicated for a lun on san storage, but your proc or memory isn't enough and or your page file is not configured correctly. Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/