Yesterday I updated from 2.08 to 2.2.1
I strive to run Zabbix without any triggers triggered, everything green.
Sometimes an item becomes "not supported".
I have a trigger for that as well and when I notice this I will go to configurations -> hosts and select "items" for 1 of the many hosts in the list.
Then I would empty the "host field" in filter and select "not supported" in state..
Now in 2.2.1 this host field is already empty, when in fact 1 of the hosts is chosen. I can't even go to that field.
This is not really a bug, but at least not that intuitive
What I can do is a reset, which somehow removes the lock on "host" and it really empties the field..
I will then get a list of all unsupported items if I set the filter to show me those.
I could live with that.... BUT,
When I select all the items and try a bulk setting to enable all these, nothing happens.
None of the items become enabled.
If I individually enable these items it works....
Not an improvement...
I strive to run Zabbix without any triggers triggered, everything green.
Sometimes an item becomes "not supported".
I have a trigger for that as well and when I notice this I will go to configurations -> hosts and select "items" for 1 of the many hosts in the list.
Then I would empty the "host field" in filter and select "not supported" in state..
Now in 2.2.1 this host field is already empty, when in fact 1 of the hosts is chosen. I can't even go to that field.
This is not really a bug, but at least not that intuitive
What I can do is a reset, which somehow removes the lock on "host" and it really empties the field..
I will then get a list of all unsupported items if I set the filter to show me those.
I could live with that.... BUT,
When I select all the items and try a bulk setting to enable all these, nothing happens.
None of the items become enabled.
If I individually enable these items it works....
Not an improvement...