CENTOS 6 With MySQL

This XML have the data from Template A (template A are linked to another template (template C) but this template C dont have prototypes and are exported without problems).

Yes such problem exists, but for now it works as designed, i.e we export only objects that are not inherited from template or are not dependent on inherited object.
Same can happen for example if you change dependencies for inherited trigger, or related applications for inherited item, these changes cannot be exported.

I move this to ZBXNEXT because it's improvement of current export functionality.

I'm using this functionality of zabbix also to avoid generating items that will become unsupported. Unfortunately I working with two zabbix installations. One testing, where I develop Templates and the other one where I have the productional montoring installed. Unfortunately at the moment I have to create These templates twice.

Is there any workaround to export template with item/trigger prototypes, in case of linked discovery rules? I need to move my new item/trigger prototypes to other Zabbix server, but I see no way to export them.

This does not only apply to item/trigger prototypes but also on overrides of normal items/triggers.

For example:

• Template A defines system.name
• Template B inherits Template A, but overrides Update Interval, Storage Period and Inventory Field of system.name
• Export Templates A and B
• Import Templates A and B on a different zabbix server (or first delete templates A and B and then import them again)
• Template B now just inherits Template A and all overrides on system.name are gone.

I've read that this is currently as designed but I think this is quite a flaw. When you export a configuration, you expect that it gets exported exactly as it is configured.

We also have 2 zabbix environments : dev and prod .. with an automatic export to git on dev and an automatic import from git to prod..

But now it turns out that those changes do not get exported .. so are not tracked in git and thus not imported in prod. Which currently even makes a few template imports fail due to overrides that should prevent conflicts are not exported..

If Zabbix wants their templates to be truly modular and world shareable, I think this issue should be addressed asap. As the only solution now is to start duplicating templates and/or integrating templates into each other to be able to define such overrides.

Meanwhile, I think the GUI at least should display a big fat warning that such things as changes on inherited items/triggers or discoveries won't be exported. As well as in de API documentation of configuration.export.

Completely agree with @robinr

We have the same issue, as templates are distributed via git. So overrides to inherited LLD or normal items/triggers do not get exported.

The workaround, we use, to this is unlinking but not clearing the template, but this means items/triggers are essentially duplicated. So this makes maintenance a nightmare, as we have to track this duplication.

This is a fundamental flaw in the export/import design. Essentially ruining the major benefit of template inheritance

Another vote to fix this.

This limitation completely destroys the usefulness of the template inheritance concept, since there really is no clean way to transport the hierarchy to another system.

Distributing those templates to other people via git is also a non starter

Adding another vote. That the additional item & trigger prototypes are missing in an export of the child template is a) causing us lots of headaches, and b) going against reasonable expectations.

Configuration loss during template export and import is awful. While entire mechanics of inheritance is acceptable, any modern deployment need a staging environments for monitoring system. It is absolutely impossible neither do an automation nor manually move templates between hosts once we are using something added to Zabbix after 1.4.x series in templates.

This really hinders adoption of Zabbix with multiple servers.

If we want to export templates from one server and import on another we cannot use inheritance and overrides at all. Adding item prototypes to inherited discovery rules does not work either.

I really hope this can be fixed.

Heres an unofficial fix.

https://github.com/X4BNet/zabbix/commit/c91d4d7266c50859b7da68dde854127385ac3458

I release this work commit into public domain. Do with it what you will under any licence or for any purpose. It comes with no guaruntees of completeness or finess of purpose.

Update: ZBX-21931 modifications of inherited triggers missing in templates' configuration export - ZABBIX SUPPORT

As of version 6.4.0 the nested template functionality will be removed, but the reported problem will still exist in host export.