Difference between revisions of "Zabbix template upgrade"
Jump to navigation
Jump to search
(Created page with "https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/444292-unable-to-update-existing-templates-zabbix-6-0-4 ``` Hi! Same problem here (upgrade from 5.4 to 6.0)....") |
|||
| Line 2: | Line 2: | ||
``` | ``` | ||
| − | + | As mentioned above upgrading from 5.x to 6.x template yaml they do not link the submodules anymore so just Unlink submodules from existing Zabbix agent active , in our case the below | |
| − | + | Linux CPU by Zabbix agent active | |
| + | Linux filesystems by Zabbix agent active | ||
| + | Linux generic by Zabbix agent active | ||
| + | Linux memory by Zabbix agent active | ||
| + | Linux network interfaces by Zabbix agent active | ||
| − | + | And then import 6.x Zabbix agent active template and it should keep working. | |
| + | https://raw.githubusercontent.com/za...ux_active.yaml (https://github.com/zabbix/zabbix/blo...ux_active.yaml) | ||
| + | I think with the new setup moving forward it should be less of a mess upgrading because of using UUIDs and not doing sub modules. | ||
| + | |||
| + | This project can be useful too though to monitor you changes. https://github.com/jeremybusk/zabbix...-export-import | ||
| + | ``` | ||
| + | |||
| + | You do NOT need to do all this but you could | ||
| + | ``` | ||
1/ Unlink (but not clear sub-module templates from "Linux by zabbix Agent Active"); | 1/ Unlink (but not clear sub-module templates from "Linux by zabbix Agent Active"); | ||
2/ delete all the old templates (sub-module from Linux + "Linux by zabbix Agent Active" + "Zabbix agent active"); | 2/ delete all the old templates (sub-module from Linux + "Linux by zabbix Agent Active" + "Zabbix agent active"); | ||
| Line 11: | Line 23: | ||
4/ Relink everything. | 4/ Relink everything. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
``` | ``` | ||
Latest revision as of 18:10, 24 July 2023
As mentioned above upgrading from 5.x to 6.x template yaml they do not link the submodules anymore so just Unlink submodules from existing Zabbix agent active , in our case the below Linux CPU by Zabbix agent active Linux filesystems by Zabbix agent active Linux generic by Zabbix agent active Linux memory by Zabbix agent active Linux network interfaces by Zabbix agent active And then import 6.x Zabbix agent active template and it should keep working. https://raw.githubusercontent.com/za...ux_active.yaml (https://github.com/zabbix/zabbix/blo...ux_active.yaml) I think with the new setup moving forward it should be less of a mess upgrading because of using UUIDs and not doing sub modules. This project can be useful too though to monitor you changes. https://github.com/jeremybusk/zabbix...-export-import
You do NOT need to do all this but you could
1/ Unlink (but not clear sub-module templates from "Linux by zabbix Agent Active"); 2/ delete all the old templates (sub-module from Linux + "Linux by zabbix Agent Active" + "Zabbix agent active"); 3/ import the 6.0 version of "Linux by zabbix Agent Active" and "Zabbix agent active". 4/ Relink everything.