Actions - Trigger Name Like

[dantheman]

Has anybody else noticed any problems with an Action when you use the Trigger Name Like and putting in a trigger such as "Server {HOSTNAME} is unreachable". It seems to have quit when I upgraded from 1.1.2 to 1.1.3. Other actions are working just fine, I was watching and the triggers change and other actions are working. Just actions that use that critera seem to be broken. If I just set an action for a host group it will send me an email when the "Server {HOSTNAME} is unreachable" trigger trips..

Right now I'm switching my actions around to use the severity level (which I think is what I'd like to use anyway, it seems like a better solution for me), but I'd still like to know if it's just me or if others are having the same problem with 1.1.3.

Thanks!

[vrtareg]

Hi

Yes i noticed this.
I have 2 actions to inform administrators about hosts up and down states.
After upgrade from 1.1.2 to 1.1.3 this actions stops to work.

Thanks
Areg

[vrtareg]

Hi

It seems that no one don't need actions and don't need to receive mails to be informed about monitored hosts status.

Waiting for 1.1.4. Hope in that version some bugs will be fixed .


Thanks
Areg

[dantheman]

The only actions that have stopped working for me are the ones that use "Like Name". The others I've tried seem to all be working.

Alexei can you confirm this?

[RandySpinaGE]

Just also confirming

I am just lately adding more and more triggers and actions.....
I am creating alarms for file systems with same mount points on many hosts.

Defining ACTIONS:
I sure see the benefit of "Trigger description like".... where {HOSTNAME} variable can be used instead of having to add an action for each host/file system combination.

It will be nice when "Trigger description like".... is fixed

Defining TRIGGERS:
HOWEVER.......LIKE-WISE It would be nice if, in the Expression field I could put for example:
{some_real_hostname:vfs.fs.size[*,free].last(0)}<"SomeNumber"

In other words, the asterisk means ANY MOUNT POINT. on this host that gets below some number of bytes left.

and MAYBE {{HOSTNAME}:vfs.fs.size[*,free].last(0)}<"SomeNumber"
Meaning any file system on ANY host Zabbix has defned

Thank you.

Runninf 1.1.3

[Alexei]

The action does work because ZABBIX substitutes macros in trigger description before checking for action confitions.

So, it does not check if "Server {HOSTNAME} is unreachable" is like "Server {HOSTNAME} is unreachable}", but it checks if "Server some_server_name is inreachable" matches the condition.

You may change the condition to something else (" is unreachable") to make it work.

[vrtareg]

Hi Alexei

In this case how it works in older versions ?
1.1.1 and 1.1.2 ?

Areg

[Alexei]

It worked before in a different way. It has been "fixed" in 1.1.3. Sorry for problems it caused, I didn't realize some users use macros in conditions.

I believe that 1.1.3-way of processing is correct one though.

[vrtareg]

Hi Alexei

Thank you for explaining situation.

Can you tell us when you plan to announce 1.1.4 release?

Thanks
Areg

[Alexei]

Initially ZABBIX 1.1.4 was planned for this week. I believe it could be released on 14-15 of November.