Availability trigger for Active Checks

[bbrendon]

I'll leave it for the moment no one seems to care but me.

Hopefully you can keep this in the back of your head and work something into future stuff.

So sum up, a nodata function that works against all keys/items associated to an agent/host would be my preferred solution. It would solve this (eventlog key), other issues i mentioned, and probably future issues.

[Alexei]

So sum up, a nodata function that works against all keys/items associated to an agent/host would be my preferred solution. It would solve this (eventlog key), other issues i mentioned, and probably future issues.

My point is different. Instead of introducing a workaround (yes, I think that the new nodata() function is the workaround in this context), I would suggest fixing of the original issue.

Unfortunately you did not provide enough details about the eventlog issue to start doing any serious work.

[bbrendon]

My point is different. Instead of introducing a workaround (yes, I think that the new nodata() function is the workaround in this context), I would suggest fixing of the original issue.

Unfortunately you did not provide enough details about the eventlog issue to start doing any serious work.

Well, I think both would be useful. Partially because agent communication and the busyness of a server seem to cause sporatic items being collected sometimes.

I'm not sure what detail to give you regarding the eventlogs. There aren't any errors. Its easy to reproduce. I've seen it on a dozen servers. Just put 10,000 events in the log, start the agent. And you'll reproduce it.

[bbrendon]

I was just thinking ...
A recent thread regarding all the connections made between an agent and a server. Apparently there is one connection made per item.

If this is the case, a busy internet connection with LOTS of stuff behind it may have issues making so many connections to a zabbix server on the internet. The experience I have on occasion which is random items not updating at random times may be the result of a busy internet connection coupled with agents creating one connection per item.

Just a thought...

[evgeny elkin]

Cause function nodata() is very useful, buh how i ditinguish 2 state of the host:
1) zabbix_agent daemon is stopped
2) host powered off
?

[Alexei]

Cause function nodata() is very useful, buh how i ditinguish 2 state of the host:
1) zabbix_agent daemon is stopped
2) host powered off
?

1. No data from active agent.ping
2. No data from active agent.ping AND no ICMP ping AND no some simple passive TCP ping

[Andreas Bollhalder]

Hello all

I have too a trigger using the nodata() function:

{_template:agent.ping.nodata(240)}=1

Today, I have upgraded to ZABBIX to version 1.4.2. After restarting the ZABBIX server, I got for all hosts implementing the trigger an OFF and then an ON message. So about 200 emails. Lucky, that I had renamed the script for sending SMS

It's clear to me, that the ZABBIX server has been down for more then 240s. Because of this, no data has been colleted within the last 240s and it has sent the messages.

Now, how I should extend the trigger to prevent this ? Using "system.uptime" from the ZABBIX server doesn't help when upgrading without restarting the whole server.

Any ideas ?

Andreas

[bbrendon]

Hm... I have this problem as well. I always have to disable all actions before restarting my zabbix server.

A few good ideas...
1. Add a mysql statement to "zabbix-server start" that disables actions BEFORE starting the zabbix-server binairies.

2. Monitor zabbix_server process start time. If its < 10 minutes, don't alert. The problem you might have here, is that the data may not get into the zabbix server fast enough to stop all of the alerts. The trigger might see data in the database, but it might be too old.

3. Alexei adds a "stabilization" paramater to zabbix_server.conf which allows you to enter the number of seconds to wait before actions start working.

I can think of a few possibly complex usages of nodata and zabbix_sender that might work as well, but now the trigger expressions are getting way too long in my head so I'm nixing the idea. KISS.

[Alexei]

This must be considered as a bug! It will be fixed.

[Andreas Bollhalder]

Hallo Alexei

Will awaiting the solution. Thanks in advance.

Andreas

[Sasha]

Thank you! This is fixed.

You may try the latest code from www.zabbix.com/developers.php

[Andreas Bollhalder]

Hello Sasha

Thank you! This is fixed.

Great news. Thank you for the effort.

Andreas

[michaeltje]

Thank you! This is fixed.

You may try the latest code from www.zabbix.com/developers.php

im experiencing the same problem with this, im currently using version 1.4.3 latest code from 15 oct. Hope you have more information for me

[dreas]

I think my question belongs to this topic. Using nodata I monitor a host to check if it's down. Every night however we create a copy of our MySQL database which locks the database for a while. During this time the data cannot be stored in the database (since it's locked) and the triggers are triggered. Is there a way to avoid this?

[Andreas Bollhalder]

Hello dreas

Either you setup the timeout for the trigger higher then the DB is locked (not that good solution) or have to use InnoDB with the Hotcopy utility to do a backup without locking (which is expensive).

Andreas