Reporting Items that become Not Supported

[anrstone]

We had a situation where a monitor has been working fine all week and then (at the critical time obviously) it changed state from Active to Not Supported and the subsequent trigger was not raised causing the usual panic and hand-wringing.

Is there anyway of detecting and hence reporting the fact that an item has changed state from Active to Not Supported?

Just to be clear when we went in and re-activated it it started working fine and has been since. Clearly having a situation where items just become Not Supported on there own is not great but at least if we could detect it that would be something. We're running Zabbix 1.8.2 with server and agents all at the same version.

Thanks

[zabbix_zen]

You could open a Request on the Zabbix tracker

[anrstone]

That's fine - though I'm not certain the system isn't working as designed. I was hoping there was a method in the triggers already that would handle this.

[anrstone]

So - by way of an update. I think the reason the Item switched to unsupported is that the value being sent back didn't conform with the type set (i.e. I had set up the item as type integer and the script being called normally returns an integer but due to an unhandled exception - my bad - it returned an error string)

That said it would be great if triggers could be raised off the back of an event like this. Firstly I would have been able to spot the system failure earlier and secondly it would better highlight underlying issues.

[simonc]

Otherwise, you could have a trigger like this :

{zabbixserv:zabbix[items_unsupported].min(600)}>0

The internal check : zabbix[items_unsupported] returns number of unsupported items.

Simon

[anrstone]

That's great - I hadn't spotted that before

Thanks