Item not supported after reboots

[smitty]

Hello all -

I'm running zabbix 2.2.5. I'm using the default "Template OS Windows" template and the associated filesystem and network interface discovery. This functions as expected.

I set up a trigger to send me alerts when an item goes into "Not Supported" state. When I reboot my windows clients, I get a lot of triggers/alerts about discovered items becoming not supported, and then going back to the expected "supported" state a minute or two later. As a result, the trigger send a lot of emails. This is extremely annoying - I'm not understanding why this is happening.

My "keep lost resources period" is the default 30 days.

I guess I could change the trigger to not send emails & just show the alert in the web interface, but it seems like these triggers shouldn't be firing in the first place..?

Also, is there a way in the web interface to easily get a list of all the items that are currently in "unsupported" state? (IE:in the main "monitoring dashboard" screen you can see the NUMBER of unsupported items, but you cant click on that number to see the details in a single screen).

Thanks in advance!

[ingus.vilnis]

Hi,

1) You can modify the Not supported trigger to fire after a while instead of instantly.

2) To get a list of unsupported items you have to ho to Configuration -> Hosts -> Items and use the filter on top of the list.
Deselect the host and groups but select the filter State : Not supported

Hope this helps.

Best Regards,
Ingus

[smitty]

Perfect - thanks for the speedy and helpful reply Ingus.