Help with CPU Check Thresholds

[C. Bensend]

> This is how I configured the service, my aim is to get an alert when
> the CPU load  ( uptime ) reaches 10% and a critical when there is a
> 20%
>
> check_command                   check_nrpe!check_load!10,4,3!20,15,10
>         flap_detection_enabled          0
>         notifications_enabled           1
>         notification_options            w,u,r,c
>         notification_period             24x7
>         check_period                    24x7
>         check_interval                  1
>         max_check_attempts              2
>         first_notification_delay        0
>         notification_interval           1
> }
>
> The problems is that I get WARN when the load is less than that:
> WARNING - load average: 1.77, 1.94, 3.04
> WARNING - load average: 2.11, 2.23, 3.45
> WARNING - load average: 1.90, 3.59, 4.34
> WARNING - load average: 5.65, 5.05, 4.86

You configured it to warn when the 15-minute average is 3.00, and
in your above four examples, the 15-minute averages are all > 3.00.
It is working like you configured it to.

The plugin's output is 1-minute, 5-minute, and 15-minute average.

Benny


-- 
"The very existence of flamethrowers proves that sometime, somewhere,
someone said to themselves, 'You know, I want to set those people
over there on fire, but I'm just not close enough to get the job
done.'"                          -- George Carlin


------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null