Zabbix Documentation 3.2

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:introduction:whatsnew320

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:introduction:whatsnew320 [2017/03/03 09:23]
martins-v adding 'configuration parameters' title as a subsection of daemon improvements
manual:introduction:whatsnew320 [2019/02/12 06:41] (current)
martins-v linking to template changes
Line 139: Line 139:
 The logic of delaying problem notifications during host maintenance has been changed. ​ The logic of delaying problem notifications during host maintenance has been changed. ​
  
-In previous Zabbix versions, it was possible to "​suppress" ​problem notifications during a host maintenance period (using the //​Maintenance status = not in "​maintenance"//​ action condition). Then, if the problem persisted, problem events were generated immediately after the maintenance. However, it was not always easy for users to understand what generated those events and why. Acknowledgement information of the original event was also lost.+In previous Zabbix versions, it was possible to skip problem notifications during a host maintenance period (using the //​Maintenance status = not in "​maintenance"//​ action condition). Then, if the problem persisted, problem events were generated immediately after the maintenance. However, since the original problem messages were suppressed, it was not always easy for users to understand what generated those events and why. Acknowledgement information of the original event was also lost.
  
 In the new version, the old mechanism is dropped. Instead there is a new option in action configuration,​ which allows to pause notifications in the host maintenance phase if you wish so.  In the new version, the old mechanism is dropped. Instead there is a new option in action configuration,​ which allows to pause notifications in the host maintenance phase if you wish so. 
Line 145: Line 145:
 {{:​manual:​introduction:​pause_escalations.png|}} {{:​manual:​introduction:​pause_escalations.png|}}
  
-If notifications are paused during maintenance,​ they get back on course ​after the maintenance,​ according to the escalation scenario. ​+If notifications are paused during maintenance,​ they get started ​after the maintenance,​ according to the escalation scenario. That means that no messages are skipped, simply delayed.
  
 See also: See also:
  
-  * [[:​manual/​maintenance|Maintenance]] 
-  * [[:​manual/​config/​notifications/​action/​escalations|Escalations]] 
   * [[:​manual/​installation/​upgrade_notes_320#​delaying_escalations_during_maintenance|Upgrade notes for 3.2]]   * [[:​manual/​installation/​upgrade_notes_320#​delaying_escalations_during_maintenance|Upgrade notes for 3.2]]
 +  * [[:​manual/​config/​notifications/​action/​operation#​configuring_an_operation|Action operations]]
  
 ==== - Viewable items, triggers, graphs created by LLD ==== ==== - Viewable items, triggers, graphs created by LLD ====
Line 277: Line 276:
 The history_text.id and history_log.id fields were removed from the corresponding history tables. Those fields were redundant and removing them will simplify history table structures and will remove unnecessary overhead when inserting values. The history_text.id and history_log.id fields were removed from the corresponding history tables. Those fields were redundant and removing them will simplify history table structures and will remove unnecessary overhead when inserting values.
  
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]