I think this might be useful for everyone:
the ability to export and import template with all trigers and items into XML document (using some generic xml library).
This will add at least 3 great features to the product
1) Ability to share templates over the internet amongst users (in the future vendors can ship their own xlm files).
2) Ability to copy templates between zabbix servers (for example to implement template in production after testing it on testing server).
3) Ability to clone templates by exporting them, changing name, and importing.
The file should have items, triggers and version of format.
zabbix +> format_version
...........L-> trigger +> item
............................| ->application
.............................L->triggers
This could be extremely useful.
the ability to export and import template with all trigers and items into XML document (using some generic xml library).
This will add at least 3 great features to the product
1) Ability to share templates over the internet amongst users (in the future vendors can ship their own xlm files).
2) Ability to copy templates between zabbix servers (for example to implement template in production after testing it on testing server).
3) Ability to clone templates by exporting them, changing name, and importing.
The file should have items, triggers and version of format.
zabbix +> format_version
...........L-> trigger +> item
............................| ->application
.............................L->triggers
This could be extremely useful.
I even heard "well, ZABBIX is a long process to configure"... with templates, we saved times, with import/export feature, this will drop times to the bare minimum !!!
Comment