Hello,
Since version 4 I have a real issue if we make a mass update and close triggers which are close able and not close able.
In case of network outage or something else:
In this case I have to acknowledge several hundreds or thousands of triggers. Some triggers must also be closed to rearm it (SNMP Traps, Eventlog, Logfiles), because theses will not become status green automatically.
In Version 3.x if I made a mass update I need not care about these triggers are close able or not close able. If only one marked trigger is close able the "close"-box was check able. All triggers which were close able were closed and all triggers which were not close able were still opened.
Now (4.x) it is reversed: If only one trigger on mass update is not close able the check box "close problem" is greyed out. So no trigger which must be closed (SNMP Traps, Eventlog, Logfiles) will be rearmed and we do not seen if a new problem comes in.
I have this issue also in daily business:
Windows: It is often that several triggers are going on error for the same root cause. e.g. Service stops unexpectedly. One trigger Service Down , one trigger Eventlog and one trigger for Logfile. Now I am not able to acknowledge these triggers in one step -> one for the close able triggers and one for the not close able.
to get out of this predicament
My really problem: If the operator does not care about this circumstance, the trigger which must be closed to rearm it is not closed, no new problems will be displayed. This trigger is acknowledged until the cows come home.
I have opened a case in the bug tracker(https://support.zabbix.com/browse/ZBX-16031), but it seems the developers does not understand my problem. "Woks as design"
To get out of this predicament. My question: Is it possible to configure a trigger that if it will be acknowledged it also be closed?
Since version 4 I have a real issue if we make a mass update and close triggers which are close able and not close able.
In case of network outage or something else:
In this case I have to acknowledge several hundreds or thousands of triggers. Some triggers must also be closed to rearm it (SNMP Traps, Eventlog, Logfiles), because theses will not become status green automatically.
In Version 3.x if I made a mass update I need not care about these triggers are close able or not close able. If only one marked trigger is close able the "close"-box was check able. All triggers which were close able were closed and all triggers which were not close able were still opened.
Now (4.x) it is reversed: If only one trigger on mass update is not close able the check box "close problem" is greyed out. So no trigger which must be closed (SNMP Traps, Eventlog, Logfiles) will be rearmed and we do not seen if a new problem comes in.
I have this issue also in daily business:
Windows: It is often that several triggers are going on error for the same root cause. e.g. Service stops unexpectedly. One trigger Service Down , one trigger Eventlog and one trigger for Logfile. Now I am not able to acknowledge these triggers in one step -> one for the close able triggers and one for the not close able.
to get out of this predicament
My really problem: If the operator does not care about this circumstance, the trigger which must be closed to rearm it is not closed, no new problems will be displayed. This trigger is acknowledged until the cows come home.
I have opened a case in the bug tracker(https://support.zabbix.com/browse/ZBX-16031), but it seems the developers does not understand my problem. "Woks as design"
To get out of this predicament. My question: Is it possible to configure a trigger that if it will be acknowledged it also be closed?