Hi! I'm on a team running Zabbix 5.2.4 for 200 users with 1,100 hosts and growing. We want to keep out-of-the-box templates up to date as newer versions are released.
I know we can get updated templates from https://git.zabbix.com/projects/ZBX/...owse/templates. And I know that importing a template with the same name as an existing template will update the existing template (assuming you leave the options to update template objects selected). That's a reasonable way to update templates that may be linked to hundreds of hosts.
However, the names of out-of-the-box templates all start with "Template App" and end with their specific template name. An example would be "Template App Apache by HTTP". This does not match the naming convention found in the version controlled templates in git.zabbix.com. Those templates just have their specific name.
Here's a couple of links to docs that talk about upgrading templates. They don't mention the difference in naming convention between out-of-the-box and git.zabbix.com templates.
What I don't understand is why the names of the out-of-the-box templates do not match the template names in git.zabbix.com? Since they don't match, someone has to rename many locations throughout the new template's yaml file before it can be imported.
Having to rename each template from git.zabbix.com before importing adds a lot of overhead to updating Zabbix over time. I was just hoping someone might point out a better way that I am overlooking.
Am I missing something? Is there an easier way to upgrade out-of-the-box templates?
Thanks to the Zabbix team for a providing a great application!
And thanks to whomever reads my long post and sheds some light on this situation!
I know we can get updated templates from https://git.zabbix.com/projects/ZBX/...owse/templates. And I know that importing a template with the same name as an existing template will update the existing template (assuming you leave the options to update template objects selected). That's a reasonable way to update templates that may be linked to hundreds of hosts.
However, the names of out-of-the-box templates all start with "Template App" and end with their specific template name. An example would be "Template App Apache by HTTP". This does not match the naming convention found in the version controlled templates in git.zabbix.com. Those templates just have their specific name.
Here's a couple of links to docs that talk about upgrading templates. They don't mention the difference in naming convention between out-of-the-box and git.zabbix.com templates.
What I don't understand is why the names of the out-of-the-box templates do not match the template names in git.zabbix.com? Since they don't match, someone has to rename many locations throughout the new template's yaml file before it can be imported.
Having to rename each template from git.zabbix.com before importing adds a lot of overhead to updating Zabbix over time. I was just hoping someone might point out a better way that I am overlooking.
Am I missing something? Is there an easier way to upgrade out-of-the-box templates?
Thanks to the Zabbix team for a providing a great application!
And thanks to whomever reads my long post and sheds some light on this situation!