Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Warning range doesn't trigger at top?
#1
I have a disk usage monitor with warning from 80-90 and critical from 91-100

at 90, it shows green...

Is this somewhere doing an (if value < max_warn) {...} thing where it should be <= or what?

I assume this is in pandora server, installed from:

pandorafms_server-4.0.2-1.noarch.rpm

 Reply
#2
Start the range for the critical min value at 90.1

Probably the module is giving a value like 90.2 or whatever between 90 and 91 which are not included in the ranges you setup so that's why it shows at normal status.

Regards
 Reply
#3
(07-30-2012, 03:50 PM)Nacho link Wrote: Start the range for the critical min value at 90.1

Probably the module is giving a value like 90.2 or whatever between 90 and 91 which are not included in the ranges you setup so that's why it shows at normal status.

Regards

The module cuts the decimal off the end.

I should just warn on 80-90 and critical on 90-100, instead of critical 91-100 anyway.  Interestingly, when you invert these (i.e. warn from 10-20, critical from 0-10), the logic changes:  Warning seems to pick up on the bottom end (10-20 warns on 10 <= x < 20).
 Reply


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnológicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes