This is the documentation page for an unsupported version of Zabbix.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

3 Nesting


Nesting is a way of one template encompassing one or more other templates.

As it makes sense to separate out on individual templates entities for various services, applications etc. you may end up with quite a few templates all of which may need to be linked to quite a few hosts. To simplify the picture, it is possible to link some templates together, in one "nested" template.

The benefit of nesting is that then you have to link only the one template to the host and the host will inherit all entities of the linked templates automatically.

Configuring a nested template

If you want to link some templates, to begin with you can take an existing template or a new one, then:

  • Open the template properties form
  • Look for the Linked templates tab
  • Click on Select to select templates in the popup window
  • Click on Add to list selected templates
  • Click on Add/Update in the template properties form

Now the template should have all the entities (items, triggers, custom graphs etc.) of the linked templates.

To unlink any of the linked templates, in the same form use the Unlink or Unlink and clear buttons and click on Update.

Choosing the Unlink option will simply remove the association with the other template, while not removing all its entities (items, triggers, graphs etc).

Choosing the Unlink and clear option will remove both the association with the other template and all its entities (items, triggers, graphs etc).

Permission issues

  • You may have a setup where an Admin level user has Read-write access to some Template A while not having Read-write access to Template B that holds Template A in a nested setup. In this case, an item created on Template A, while inherited by the hosts of Template A, will not be inherited by the hosts of Template B. Thus, creating a trigger for such an item will fail altogether, because of missing corresponding items on hosts of Template B.