Handling unsupported with triggers

[kefear]

Hello,
Yesterday we had troubles due to bad access-list configuration. Because of that some items became unsupported and didn't trigger at all. I've been searching this forum for any solution but found nothing except monitoring number of unsupported_items which is not reliable. Has anyone know some solutions/workarounds concerning this issue ? Or maybe there is some development in progress ?
Thank in advance for any help
Have a nice day

[qix]

Well, you could set the retry time lower so the item will be polled sooner.

[kefear]

Heh, You didn't understand me
We want to know ASAP when item becames unsupported (i.e. zabbix has problems with retrieving snmp data for some reason).
I have made some workaround. It bases on difference between current time and the time last value has been retrieved (lastclock on items table). When the difference is above some value it triggers an alarm. Whole check uses zabbix_agent on zabbix host. It looks like this:

"select host from hosts where hostid in ( select hostid from items where UNIX_TIMESTAMP(NOW()) - lastclock > 1800 and status=0 and type=4) and status=0"

status 0 means that host and specific item is enabled
type 4 means it is normal SNMP check (not zabbix trapper or other)

It is just very basic idea which can be extended to anyones needs.