how to see why trigger did not create an alert

[lulu]

Hi,

I'm new to Zabbix.
I'm trying to figure out the easiest way to test / debug triggers defined for a specific host

Is there a log that has value of trigger expressions when they were triggered?

tia

[mortuletti]

Hi!
All Trigger status changes is logged in to the Monitoring - Events.
Br, Alexander

[lulu]

thank you. I'm using Zabbix 2.4. How difficult is it to upgrade to the latest version?

[lulu]

thanks. Is "Monitoring - Events" available in Zabbix 2.4?

[Linwood]

I think it's a great question though; you can see the changes in events, but it is sometimes hard to tell why they fire, or even worse why they do not. More precisely it is sometimes hard to figure out what the various expression values actually calculated, especially when there are statistical functions involved. I'm trying to track down one right now for NTP monitoring, for example.

One thing I've done at times, which is tedious, is to create calculated items with the same functions as are in the triggers, and at the same or faster intervals, so you have a record of what they all were at each trigger change.

Debug of course is a possibility, but with anything but a handful of items you get buried in data, and with too much I think it slows the system down unacceptably. I really wish there were a "debug one host" or something similar.

You can also include function values inside of actions (e.g. that send email), like:

{{HOST.HOST}:icmppingsec.min(5m)}

If the trigger is dependent on (for example) numerous functions, and it fires unexpectedly, this can let you see each function's value when it fired. Of course that is not helpful if you are trying to find out why it does NOT fire, which is why I create temporary calculated items.

[lulu]

You can also include function values inside of actions (e.g. that send email), like:

{{HOST.HOST}@@@icmppingsec.min(5m)}

If the trigger is dependent on (for example) numerous functions, and it fires unexpectedly, this can let you see each function's value when it fired. Of course that is not helpful if you are trying to find out why it does NOT fire, which is why I create temporary calculated items.

These are some great ideas, thank you for sharing!

[Linwood]

These are some great ideas, thank you for sharing!

Sorry, I had a typo in my example (the "@@@" was substituted for a ":" for a long involved reason in where I copied it from).

[Linwood]

thank you. I'm using Zabbix 2.4. How difficult is it to upgrade to the latest version?

I didn't find it hard (I came from 2.4.6), though I built from source. I do not think it helps with this issue however (though there are a lot of nice features).