not-in-maintenance-or-zabbix-servers.png
|
Duplicate |
Team B
[ZBX-13344] Default condition for trigger based actions Created: 2018 Jan 16 Updated: 2024 Apr 10 Resolved: 2018 Jun 12 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 3.4.6 |
| Fix Version/s: | 3.4.8rc1, 4.0.0alpha5, 4.0 (plan) |
| Type: | Incident report | Priority: | Major |
| Reporter: | Alexey Pustovalov | Assignee: | Alexander Vladishev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | action, maintenance, trigger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
not-in-maintenance-or-zabbix-servers.png
|
||||
| Issue Links: |
|
||||
| Team: | Team B |
||||
| Sprint: | Sprint 29, Sprint 30, Sprint 35, Sprint 36 | ||||
| Story Points: | 0.25 | ||||
| Description |
|
Currently new actions based on triggers have one predefined condition: "host not in maintenance". It does not work with "Pause operations while in maintenance" which is enabled by default as well. If both options are enabled Zabbix does not send notifications after maintenance period ends. So Zabbix frontend should create new actions without "host not in maintenance" condition at all. |
| Comments |
| Comment by Lorenzo Panichi [ 2018 Mar 20 ] |
|
I think that another point that makes "host not in maintenance" not a nice default at all is the fact that even without using "Pause operations while in maintenance" feature it won't work as expected - or at least as it used to - because you won't get any extra event in case the trigger is still in problem state at the end of the maintenance period. |
| Comment by Andrejs Griščenko [ 2018 Mar 23 ] |
|
Fixed in:
|
| Comment by Alexander Vladishev [ 2018 May 07 ] |
|
(2) [F] Documentation needs to be updated.
natalja.cernohajeva: necessary documentation update has been executed. Affected pages:
(removed note mentioning default setting, updated information in Maintenance status section) RESOLVED sasha Do not need to update information in Maintenance status section.
In some cases this can be not true. For example,
In that case notifications will be send for all "Zabbix servers" or for hosts in non-maintenance status. REOPENED
natalja.cernohajeva: Removed this information from Maintenance status section. Before that the note (When a new action for triggers is created, it gets one condition automatically: "Maintenance status = not in //maintenance//". With this condition notifications are not sent for hosts in maintenance. This condition can be removed by the user.) which is not valid any more was also removed. RESOLVED sasha In general, this is true. But users may misinterpret this. Therefore, it is better to remove it from the documentation. Thanks! CLOSED |
