Whats is an acceptable range for DISK_READ and DISK_WRITE for monitoring Exchange?

Im currently monitoring Exchange with WhatsUp Gold. I set up an exchange active monitor and it give me the option to set a range. I left it at default but i need to get an experience tech that knows exchange 2007. This is the notice i get back.

MonExchange:DISK_READ=[The value 10654.56 is out of the acceptable range of 0.00 through 5120.00.]
MonExchange:DISK_WRITE=[The value 6135.99 is out of the acceptable range of 0.00 through 5120.00.]
I set this to 5120.00 thinking this would stop giving us alerts so often. I would disable this but i would like to know when resources are running high that would affect performance on our users. So if someone would please let me know of an acceptable range to let me know when performance is running high but with out getting notices every five minutes. I thnk you in advance.
jbailey82Asked:
Who is Participating?
 
defkamelConnect With a Mentor Commented:
Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .020 (20 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .050 (50 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

CAS Servers overall should not be disk intensive as most operations should be handled in memory. If excessive disk use is found, then we either have too much load on the server or more memory is needed to handle the overall load.<br>

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .020 (20 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .050 (50 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

CAS Servers overall should not be disk intensive as most operations should be handled in memory. If excessive disk use is found, then we either have too much load on the server or more memory is needed to handle the overall load.<br>

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.