Problems with action conditions

[xibbaz]

Our desktops at our DRP all reboots at 00:02 and thus at that time every week day we get loads and loads of alerts (rebooting, unreachable, ...).

I downgraded the rebooting trigger to warning for which we are not alerted, but I still wish to know when a machine is unreacheable outside the 00:00 to 00:03 time window.

I tried to filter this by modifying the "send message" action with conditions in this manner:

Type : AND
(A) Host group <> "Windows desktops"
(B) Trigger description not like "is unreacheable"
(C) Time period not in "1-7, 00:00-00:03"

Well, you guessed it, this has absolutely no effect. All alerts are sent even between 00:00 to 00:03.

For tonight, I'm trying replacing (B) with:
(B) Trigger <> "Template_Windows is unreachable"

[tighep]

You can accomplish this by teaching the trigger not to fire between 00:00 and 00:03. It'll look something like this:

{host1:vfs.file.exists[/etc/passwd]. time( 0 ) }>000300

That would only fire the trigger if it's after 00:03:00 in time.

[jgerry]

Interesting solution, but doesn't really answer the question. Why don't the conditions in Actions work as expected?

My data points -- I find the conditions in any Action to be almost entirely useless. I cannot make them work reliably, if at all. It's incredibly frustrating.

I find the "Time Period" conditional to be especially twitchy. One hint which may help people -- the time period you enter matches the monitored server's local time. Not GMT, UMT, or your Zabbix server time... Local server time. No where is this documented, btw.

The naming conventions for some of the Action conditions are confusing too... There's one called "Trigger Description", which, I think, refers to the "Comments" section of the trigger config. It would be a lot more clear if they just used the same nomenclature -- either name the condition "Trigger Comments" or name the comments field "Description". This also isn't documented anywhere.

[bashman]

The naming conventions for some of the Action conditions are confusing too... There's one called "Trigger Description", which, I think, refers to the "Comments" section of the trigger config. It would be a lot more clear if they just used the same nomenclature -- either name the condition "Trigger Comments" or name the comments field "Description". This also isn't documented anywhere.

You're totally right the Trigger Description refers to the trigger comments field not to the trigger name field.

http://www.zabbix.com/forum/showthread.php?p=64068#post64068

Thank you.

[zalex_ua]

..... the Trigger Description refers to the trigger comments field not to the trigger name field.

This is a mistake! According to current documentation Trigger Description refers to the Trigger name field !
I hope that the inconsistency of names will be fixed in this issue https://support.zabbix.com/browse/ZBX-2755

[bashman]

Thanks zalex_ua,

The documentation is clear about that, but is it really working like that?.

I'm not sure if "Trigger description" condition works as it should, I remember I used to add the trigger name in the trigger comment first line, in order to make the condition work.

I can't reproduce it.

[zalex_ua]

The documentation is clear about that, but is it really working like that?.

I'm not sure if "Trigger description" condition works as it should

I tested "Trigger description" condition before my first answer, it works right as it should !!!

I remember I used to add the trigger name in the trigger comment first line, in order to make the condition work.

I can't reproduce it.

Stop doing this wrong action, you can get confused. It is better to clear comments. I recommend following the change of actions, triggers, items always wait at least one minute before the experiments. In zabbix very powerful config caching system (by default cache is updated every 60 seconds), this should be remembered.

[bashman]

Right, thanks again.

I tested it again and no problem, it works fine.

[subba5678]

I tested "Trigger description" condition before my first answer, it works right as it should !!!



Stop doing this wrong action, you can get confused. It is better to clear comments. I recommend following the change of actions, triggers, items always wait at least one minute before the experiments. In zabbix very powerful config caching system (by default cache is updated every 60 seconds), this should be remembered.

Hi Zalex_ua,
I configured the Triggers in a way that it needs to triggers only "High" Severity alerts .But it is triggering the alerts even if the severity is in "Warning" . Please help me out so that it needs to trigger only with the "High" Severity. Please find the attachment of my trigger Configuration.Even i followed this . Please help me out

http://www.zabbix.com/documentation/...config/actions

Thanks,
Subbu

[zalex_ua]

Please find the attachment of my trigger Configuration.Even i followed this . Please help me out

Not sure if I can help you. Are you sure that the alerts are coming just from the action "DFW"? Maybe alerts come from a completely different action?
Are you sure that the alerts come only from the hosts of the "DFW" group?
I recommend adding some unique text in the message body to make sure it come exactly from the action "DFW".

Be careful with Recovery message option.https://support.zabbix.com/browse/ZBXNEXT-452

[subba5678]

Hi zalex_ua,
Thanks for the reply , Yes the alerts are comming from DFW Group .Please find the screen shot for reference.Please help me out


Thanks,
Subbu

[zalex_ua]

Please help me out

Sorry, http://catb.org/~esr/faqs/smart-questions.html

[bashman]

Try to add Trigger value = "PROBLEM" to your action conditions and tell us how it goes.

[subba5678]

Hi Bashman,
Thanks for the reply , I added the Trigger Value= Problem , then also it is triggering the Warning Alerts . For reference please find the screen shot. Also please find the email Description

SNMP service on BLR-NOC-06: PROBLEM

Status: PROBLEM
Host: BLR-NOC-06 (172.25.100.183)
Severity: Warning

Event ID: 51165
Event Time: 2010.10.14 - 15:22:49
Event Duration: 0m

Alert Details:
SNMP service on BLR-NOC-06
If the Status: OK , Ignore the alerts

Last Item Value:
Stopped (6)




Thanks,
Subbu