1 Configuring a template
Overview
Creating a template
To create a template, do the following:
- Click on Create template.
- Edit template attributes.
The Templates tab contains general template attributes.
All mandatory input fields are marked with a red asterisk.
Template attributes:
The Tags tab allows you to define template-level tags. All problems of hosts linked to this template will be tagged with the values entered here.
User macros, {INVENTORY.*} macros, {HOST.HOST}, {HOST.NAME}, {HOST.CONN}, {HOST.DNS}, {HOST.IP}, {HOST.PORT} and {HOST.ID} macros are supported in tags.
The Macros tab allows you to define template-level as a name-value pairs. Note that macro values can be kept as plain text, secret text, or Vault secret. Adding a description is also supported.
For convenience, links to the respective templates, as well as a link to global macro configuration is provided. It is also possible to edit a linked template macro or global macro on the template level, effectively creating a copy of the macro on the template.
The Value mapping tab allows to configure human-friendly representation of item data in value mappings.
Buttons:
Add the template. The added template should appear in the list. | |
![]() | Update the properties of an existing template. |
Create another template based on the properties of the current template, including the entities (items, triggers, etc.) inherited from linked templates, but excluding template vendor and version. | |
![]() | Create another template based on the properties of the current template, including the entities (items, triggers, etc.) both inherited from linked templates and directly attached to the current template, but excluding template vendor and version. |
Delete the template; entities of the template (items, triggers, etc.) remain with the linked hosts. | |
![]() | Delete the template and all its entities from linked hosts. |
Cancel the editing of template properties. |
Adding items, triggers, graphs
Items have to be added to a template first. Triggers and graphs cannot be added without the corresponding item.
To add items to the template, do the following:
- Go to Data collection → Hosts (or Templates).
- Click on Items in the row of the required host/template.
- Mark the checkboxes of items you want to add to the template.
- Click on Copy below the item list.
- Select the template (or group of templates) the items should be copied to and click on Copy.
All the selected items should be copied to the template.
Adding triggers and graphs is done in a similar fashion (from the list of triggers and graphs respectively), again, keeping in mind that they can only be added if the required items are added first.
Adding dashboards
To add dashboards to a template in Data collection → Templates, do the following:
- Configure a dashboard following the guidelines of .
The widgets that can be included in a template dashboard are: classic graph, graph prototype, clock, plain text, URL.
Configuring low-level discovery rules
See the section of the manual.
Adding web scenarios
To add web scenarios to a template in Data collection → Templates, do the following:
- Click on Web in the row of the template.
- Configure a web scenario following the usual method of .
Creating a template group
Only Super Admin users can create template groups.
To create a template group in Zabbix frontend, do the following:
- Go to: Data collection → Template groups.
- Click on Create template group in the upper right corner of the screen.
- Enter the group name in the form.
To create a nested template group, use the ‘/‘ forward slash separator, for example . You can create this group even if none of the two parent template groups (Linux servers/Databases/
) exist. In this case creating these parent template groups is up to the user; they will not be created automatically.
Leading and trailing slashes, several slashes in a row are not allowed. Escaping of ‘/‘ is not supported.
Once the group is created, you can click on the group name in the list to edit group name, clone the group or set additional option:
Apply permissions to all subgroups - mark this checkbox and click on Update to apply the same level of permissions to all nested template groups. For user groups that may have had differing assigned to nested template groups, the permission level of the parent template group will be enforced on the nested groups. This is a one-time option that is not saved in the database.
Permissions to nested template groups:
- When creating a child template group to an existing parent template group, user group permissions to the child are inherited from the parent (for example, when creating if
Databases
already exists).