manual:installation:template_changes

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:installation:template_changes [2021/01/27 21:18]
127.0.0.1 external edit
manual:installation:template_changes [2021/05/14 15:08] (current)
marinagen [ZBXNEXT-6411] New uniqueness criteria for templates
Line 8: Line 8:
   * Then, while in //​Configuration//​ -> //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).   * Then, while in //​Configuration//​ -> //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).
  
-=== New templates ===+=== CHNAGES IN 5.4.0 === 
 + 
 +== New templates == 
 + 
 +See the list of [[:​manual/​introduction/​whatsnew540#​new_templates|new templates]] in Zabbix 5.4.0 
 + 
 +== New uniqueness criteria == 
 +All templates themselves and template elements such as items, triggers, discovery rules, dashboards, etc. have been assigned unique IDs.These IDs are used to match templates being imported with existing templates and therefore allow to rename a template, change trigger expression, etc. by import without the template or trigger being recreated. 
 + 
 +During the upgrade all elements with the same unique identifiers (such as template name for a template or item key for an item) will receive the same UUIDs across all installations. This is done to allow future updates of templates from the same source installations. The same UUIDs will be assigned to elements when importing templates from older versions.  
 + 
 +After the upgrade, any element created on 5.4.0rc1 version or later will have a unique UUID assigned to it and these UUIDs will be different across the installations. Upon linkage of a template all elements, that become inherited, will lose their UUIDs. Upon unlinkage without clear, all now independent elements will receive newly generated UUIDs. 
 + 
 +Templates without element IDs can still be imported, in this case, new random element IDs will be generated for new template entities for temporary use.
  
-See the list of [[:​manual/​introduction/​whatsnew540#​new_templates|new templates]] in Zabbix 5.4.