Action Disabled , but no info on the audit log

[andrea.g.els]

zabbix 3.4.8 on centos 7.
I've got a strange issue this weekend :
I've found one action disabled , re-enabled it and in the audit log I've found only the enable action.
No recent updates on zabbix (rpm pinned) , os updated friday.
One week ago the action was enabled (found the log of the actions performed).
Any idea ?

[DmitryL]

First of all - https://support.zabbix.com/browse/ZBX-2815
Second thing - If one of the entities used in Action conditions (as example Host group), gets deleted from the frontend. Action turns it state to Disabled, without any notifications or lines in the log.

[andrea.g.els]

you nailed it!

Second thing - If one of the entities used in Action conditions (as example Host group), gets deleted from the frontend. Action turns it state to Disabled, without any notifications or lines in the log.

one of the entities was a discovered hypervisor (we had an alarm tied to the number of guest vms) .
Is this behavoir by design?

as the esxi come and go , there's a smarter way instead of putting the single esxi into the action?

[dimir]

You could use host group in action.

[andrea.g.els]

as the esxi come and go , there's a smarter way instead of putting the single esxi into the action?

I was unclear in my previous post.
Into the action I have a single host (it's a command executed on an external host , not one esxi).
My problem was with the trigger part of the action:
I've got

Trigger = esxi2 : VM number alert (C) or esxi3 : VM number alert (C)

I was asking if there is a way to specify something like Trigger = esxi* : VM number alert
So far I've tried with

Trigger name like [I]VM number alert[/I]

but no luck
any idea?

[dimir]

Why no luck? Could you show the screenshot of your action configuration? Sounds like you could have combination of "Trigger name like ..." and "Host group = ...".

[andrea.g.els]

ok , after a couple of tests now it works .
Only the trigger name is needed , as the action will not be applied to an host group but to a single linux host (the application host)
many thanks