Zabbix Documentation 4.4

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:whatsnew440

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:whatsnew440 [2020/02/03 09:25]
martins-v changing instructions for getting updated templates
manual:introduction:whatsnew440 [2020/02/04 08:51] (current)
marinagen
Line 247: Line 247:
 === MySQL/​MariaDB === === MySQL/​MariaDB ===
  
-  * //Template DB MySQL// - see [[:​manual/​config/​templates_out_of_the_box/​requirements/​mysql#​steps|requirements for operating]] this template.+  * //Template DB MySQL by Zabbix agent// - see [[:​manual/​config/​templates_out_of_the_box/​requirements/​mysql#​steps|requirements for operating]] this template. 
  
 === PostgreSQL === === PostgreSQL ===
Line 256: Line 257:
  
   * In //​Configuration//​ -> //​Templates//​ in new installations;​   * In //​Configuration//​ -> //​Templates//​ in new installations;​
-  * If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates|Zabbix Git repository]]. 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).+  * If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates?​at=refs%2Fheads%2Frelease%2F4.4|Zabbix Git repository]]. 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).
  
 ==== Internal knowledge base ==== ==== Internal knowledge base ====