This is a tag-specific summary from the official Zabbix guidelines documentation, based on the situation as of Zabbix 6.0 LTS.
Note: “Please note that this model might become enforced in the future Zabbix releases. Templates that do not follow specified rules will need to be updated.“
Tag name and value format
- lowercase only
- allowed characters: 0-9, a-z, hyphen, underscore, dot (note: space is not listed as allowed)
- hyphen preferred for word separation (“my-app”) instead of underscore (“my_app”)
- UTF-8 is supported but ASCII is preferred
Commentary: I wonder why the conversion from item applications in Zabbix 5.0 to tags in Zabbix 6.0 then automatically applied tags with name “Application” and not “application“.
Tag name: class
Tag name: target
Value: some reference to the product or brand name and model number, as suitable
At least one class and one target tag is mandatory for all templates.
Commentary: The tags that are set in the template will be inherited to all problems that occur in all hosts using the template.
No specific host tags (or other configurations) are specified in the guidelines. In practice it can make sense to configure host tags when you want to attach for example some location information that cannot be configured already in the templates.
Host tags are inherited to all problems that occur for the host.
Tag name: component
At least one component tag is mandatory for every item.
Tag name: scope
At least one scope tag is mandatory for every trigger.