Threshold settings - best practices

Question

Hi, we're looking into reviewing our current network's threshold settings for cpu, memory, packet loss, response time, etc.

Currently we put waring marks on cpu, memory, and disk usage at 80%, and high alert at 90%.

Is there any general IT standard for these numbers? What numbers do you guys use for your networks?

Thanks!

adatole · Accepted Answer

Honestly it's going to vary from machine to machine, app to app and situation to situation.

For example, MS-SQL automatically allocates 80% of the machine's RAM. It doesn't matter how much you give it. So alerting at 80% across the board is going to wake up (and piss off) your dba's.

Some machines run "hot", or run hot when performing certain operations (weekly full backup! and an antivirus scan! and month end reports! all in the SAME WINDOW).

Setting the thresholds on a machine by machine basis, with a default if that individual setting is blank, may be a more effective way to go.

Threshold settings - best practices

Top Replies