[Bigsister-general] cpu check not ok

[Rob Verduijn <suppressed>]

Hi there everyone,

I've got a little problem with the bigsister cpu check.

I've seen it on the forum before, but never saw a real sollution to the
problem.

It's the problem of the cpu check saying there is 0 idle time and
therefore it returns a red dot, but the system is doing nothing at the
time.

I used the following work around:
I've turned it into a yellow one by editting uxmon-net on the client as
follows

DEFAULT community=public frequency=5 perf=5 ALL
DEFAULT version=1 proto=udp rpc
DEFAULT proto=udp ping
DESCR features=unix,linux localhost
localhost(fil004-server) memory cpuload

### the following line does the trick of preventing a red dot
localhost(fil004-server) idle_red=-1 idle_yellow=10 load

localhost(fil004-server) disk
localhost(fil004-server) syslog
localhost(fil004-server) speed=100Mb/s network
localhost(fil004-server) proc=sshd procs proc=xinetd procs
localhost(fil004-server) proc=sendmail procs proc=_mprosrv procs
proc=cupsd procs
localhost(fil004-server) proc=_progres min=0 procs
localhost(fil004-server) proc=nscd min=0 max=0 procs
localhost(fil004-server) users
localhost(fil004-server) proc=dhcpd procs
bigsister.peros.org bsdisplay
include include_checks.$HOST


I also edited the bb_event_generator.cfg on the server:

*.* prio=40 down=yellow up=green delay=5 check="$host.conn and ((not
'$router') or $router.conn)" norepeat=20 keep=1 mail=alarm repeatprio=10
msgmax=60
*.conn prio=80 check="not '$router' or $router.conn"

# the following line is the magic line
*.cpu prio=20 check="1" delay=20 down=red

*.disk prio=60 check="1" delay=0
*.msgs check="1" delay=0

All seems fine, but since we started using bigsister we have added a
couple servers and every 20th server gives a permanent yellow dot below
the cpu check in my bigsister monitor screen.

and since we have passed 220 servers a while back you can imagine that
the amount of permanent yellow dots is starting to fill the entire big
sister monitor screen.

This makes the yellow dot a bit useless, since people start ignoring it
because its a false alert.

That is bad.

When there is a true alert they will also ignore the yellow dot, cause
they think it is probably a false cpu alert.

Does anybody know how to get a functianal cpu check, that goes red if
the proc stays on 100% usage for x minutes/hours?

Regards
Rob





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bigsister-general mailing list
suppressed
https://lists.sourceforge.net/lists/listinfo/bigsister-general