Intentionally setting item to not supported on external checks

[MNfromH]

Hi everyone,

This might sound a bit stupid first, but: Do you know a way to intentionally set an item collected by a external check to "Not supported"?

We're using a lot of custom items collected by various external checks. If I was to monitor each item for being functional, I'd have to return a string, say "ITEM_BROKEN", and have a seperate trigger to monitor each item for this string. This is a lot of overhead.

Is there any string, exit code or what not we can use to inform the zabbix-server that it should set an item to not supported?
This way, I'll get notified about it along all other not supported messages. A very clean solution I'd say.

So far I''ve simply tried to echo "ZBX_NOTSUPPORTED". But this just gets saved as the items value.

Any ideas?

[kaspars.mednis]

Hello !

have you looked at https://www.zabbix.com/documentation...types/external ?

Note that in Zabbix versions 3.4.0-3.4.2 the exit code is checked for execution result. In these versions, the item will become unsupported if the execution exit code does not match 0 (zero).

best regards,
Kaspars