Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-11125

steps:

test "{test1:agent.ping.nodata(0)}=1"

expected:
Server shows invalid fist parameter error

steps2:

test "{test1:agent.ping.nodata(5)}=1"

Expected:
There are no more errors and trigger works as before, if you kill agent you get your trigger activated after 5 seconds.
Reactivate agent and trigger resolves

Server side successfully tested. It should be documented that nodata(0) is not valid.

martins-v Interestingly the documentation already says that "The period should not be less than 30 seconds." So is it untrue for 2.0-3.2 then?

sasha It because timer process calculates such trigger functions every 30 seconds.
First parameter of nodata() function can be less than 30 seconds, but it won't give the expected effect.

glebs.ivanovskis But nodata() can also be used in calculated items, where update interval is set by user and parameter values less than 30 seconds can actually make sense.

martins-v Thanks for all the explanations.

Documented in Trigger functions for 3.4.

sasha Copied changes to 3.0 and 3.2. CLOSED

there's one case where nodata(0) could be useful - let's say somebody has a bunch of items, and they want to alert on items that have received a value at least one, but have no data now. something like this could do it :

{h:i.nodata(0)}=0 and {h:i.nodata(300)}=1

if that sounds useful to somebody, they should probably open a new feature request to revert the changes in this issue

Such functions nodata(0) can produce heavy load on the database. This undocumented functionality must be dropped.

thanks for the update, that's a good reason. it could probably be worked around by introducing an item-level property "has received data", but the need for such feature doesn't seem to be there yet.

API is ready for testing.

Server side was successfully tested.

(1) No translation string changes.

sasha CLOSED

Frontend TESTED

Released in:

• pre-3.0.6rc1 r63397
• pre-3.2.2rc1 r63396
• pre-3.3.0 (trunk) r63395