disabling nodata tricker after host not monitoring

[fips]

Every time if I disable the monitoring of a host for more then the time specified in the nodata trigger, I will get a trigger action if I reenable the host.

Example: {PC:icmpping.nodata(300)}=1

Disabling the host for more then 5 minutes will trigger an action. The behavior is logical correct, but I dont like to have this trigger action, because it was me who disabled the host for monitoring.

Is there some way to enable a trigger after some time? Can I get the value for host enabled time? Some other suggestion on how to surpress the fist trigger action after enabling the host?

Thanks for help!

[fips]

no one has this problem

No one has this problem, or no one ever tried to disable a host with a trigger like this for 10 minutes:

{Template_Linux:agent.ping.nodata(600)}

For me it is the same problem as mass alarms after enabling zabbix server. I really like to know how i can suppress the trigger firing after enabling the host in the zabbix web gui!

[HullZabbix]

I don't get this problem on any of my items.

Though I'm using

{TemplateServers:icmpping[].nodata(180)}=1

Notice the []. I've no idea if this makes a different, but it may help

[fips]

icmpping not working too

Hello
I tried your trigger and I have the same problem as with agent.ping.
Did you disable your host for more then 180 seconds to test it will trigger afterwards?

Thanks for your reply anyway. Maybe I have to find out what is wrong with my 1.8.8 version.

And here the prove:

[HullZabbix]

Yes I disabled it for longer 180.

I'm on 1.8.6

Sorry I can't be of further help

[fips]

same problem on new install

I installed zabbix on a new virtual machine and I get the same probem!!!

[robertkarl]

Solution ?

Did you ever get a solution on this ???

I have the same problem...

When I put a host on maintenance period for more than 5 minute, trigger nodata fire it up when the maintenance is over... very annoying,.


Thanks