hysteresis or dependency?

[cirrhus9.com]

Hello:

I have the following 2 custom triggers

CPU Load on {HOSTNAME} - Warning - {HOSTNAME:system.cpu.load[].last(0)}>6
CPU Load on {HOSTNAME} - Critical - {HOSTNAME:system.cpu.load[].last(0)}>10

If the CPU Load goes from 00.x to 10, I and the client get 2 notifications.

The problem now becomes do I use hysteresis or a dependency to eliminate the Warning if the CPU Load goes to the Critical threshold?

Or is there another way?

I of course, am only summarily acquainted with hysteresis, so I would need a replacement trigger and an indication of which one it would replace.

Thank you all for your time.

[acarr]

What you're looking for in your situation is Dependency.

Configure your warning trigger so that it is has a dependency on your critical trigger, therefore if your load hits critical, the warning trigger will be dropped in place of the critical one.
So, the least significant trigger is the one you create the trigger dependency on, depending on the more significant trigger.

Hysteresis is suited for where you want your triggers to set at a high point but not return back to normal until measurements are a fraction lower than that high point. For example, you hit your CPU load warning at 6, but you might want that alert to remain active until CPU load has lowered below 5.

[cirrhus9.com]

Thanks acarr but I just removed one of the triggers.

[netmon]

For the archives, you could also do something like:

CPU Load on {HOSTNAME} - Warning - {HOSTNAME:system.cpu.load[].last(0)}>6&{HOSTNAME:system.cpu.load[].last(0)}<11
CPU Load on {HOSTNAME} - Critical - {HOSTNAME:system.cpu.load[].last(0)}>10

Warning if cpu load is higher then 6 and lower then 11.

For values 7-10 Warning Trigger goes off.
For values 11+ Critical Trigger goes off.


:-)

[cirrhus9.com]

Thanks netmon.

I got a similar trigger from the crew on #zabbix