nodata() on unsupported items is not supported in zabbix 3.0 (as can be seen in one of your screenshots), that arrived in 3.2

Thanks for your reply @richlv. I agree with you, It is an important feature : Zabbix must be capable to warn when an item is not reachable/supported.

• Is it planned for Zabbix 3.0.9 or after ?
• A patch can be apply for Zabbix 3.0.X ?

So with Zabbix 3.0.7, a bypassing is possible but not really compliant, I can add a :

zabbix[host,,items_unsupported]

and create two triggers :

1. First => if items_unsupported > 0
2. Second => if items_unsupported has changed.

Thanks,
Maxime

Hello,

richlv ?

Thanks,
Maxime

You could write a check yourself. Here is SQL for all enabled hosts and triggers:

    SELECT
        h.host,
        t.description,
        t.error
    FROM
        triggers as t
    join
        functions as f
            on f.triggerid = t.triggerid
    join
        items as i
            on f.itemid = i.itemid
    join
        hosts as h
            on i.hostid = h.hostid
    WHERE
        t.error <> ''
        and h.status = 0
        and h.proxy_hostid is null
        and t.status = 0;

And here is an example for unsupported items:

SELECT hosts.host, items.key_, items.error 
FROM items
    left join hosts on items.hostid = hosts.hostid 
WHERE items.error <> ''
    and hosts.status = 0
    and hosts.proxy_hostid is null
    and items.type not in (5, 15)
    and items.status = 0;

I myself gather this data and send it to separate item on each host with appropriately configured trigger.

this issue tracker is for bugreports - please see http://zabbix.org/wiki/Getting_help for support options

Thanks Paskal for your support and this bypassing.
To my mind this is really a bug precisely on nodata() function for triggers.
So I suppose I won't be fix on Zabbix 3.0 .

Maxime

Closing as Duplicate of ZBXNEXT-1791.