cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 7

Threshold settings - best practices

Jump to solution

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!

0 Kudos
1 Solution
Level 18

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.

Leon Adato | Head Geek
------
"Measure what is measurable,
and make measurable what is not so." - Gallileo

View solution in original post

4 Replies
Level 13

He is correct in that it will vary from device to device.  The best bet is to collect data for some time and then go back and evaluate per device what values have been seen.  Then setting threshold per device can become quite useful.  Since SW has not provided this feature, another Thwack person made this post about how to do it via custom properties.

Hope it helps

Sohail Bhamani

Loop1 Systems

http://www.loop1systems.com

0 Kudos

Hey, that's not ANOTHER thwack person, that's ME!!

Seriously, thanks for quoting my stuff.

- Leon

Leon Adato | Head Geek
------
"Measure what is measurable,
and make measurable what is not so." - Gallileo

Ha!!  I completely missed that!  Its a great post!

Sohail Bhamani

Loop1 Systems

http://www.loop1systems.com

0 Kudos
Level 18

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.

Leon Adato | Head Geek
------
"Measure what is measurable,
and make measurable what is not so." - Gallileo

View solution in original post