Ad Widget

Collapse

Item not supported after reboots

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Wanhedaking
    Banned
    • Aug 2019
    • 1

    #1

    Item not supported after reboots

    Hello everyone,,
    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!
Working...