Host Down Trigger and Auto-Registration

[aboyne]

My infrastructure is out in the cloud, and it is quite often that we are adding/removing instances.

All of our agents are active and they auto-register when the instances come up. When we take machines down, we remove them from Zabbix with the API.

This all works great, except for one trigger I have set up:

{Template Linux - Active:agent.ping.nodata(30)}=1

After auto-registration, this trigger immediately goes into PROBLEM, and doesn't come out for about a minute and a half.

I know I can set a delay for the emails be modifying the action, but I don't really want to do that. Does anyone have any other ideas on how I can fix this trigger?

Thanks!

[richlv]

this might be fixed by https://support.zabbix.com/browse/ZBX-4476 for 2.2 - but make sure to test it

[Pada]

wow!

This same issue has been giving me quite some grief the past couple of months. I did some tricks to bypass this issue, but it just caused me more harm than good to try supress that alert.

Would there be an upgrade path for from 1.8 to 2.2, or would we have to upgrade to 2.0 first, because so far I don't see that much of a reason to upgrade to 2.0 yet, but 2.2 looks promising so far.

[richlv]

you have to upgrade from one version to the next one, you can not skip versions inbetween. you don't really have to run 2.0, though, you can just upgrade "through" it

[Pada]

Thanks richlv !

I think we'll then just do the "upgrade through 2.0"

[aboyne]

Thanks Richlv! We have been debating doing the upgrade right now, but we will keep this in mind when deciding.