template: pros and cons

[BusteR81]

for 1.4 zabbix, for eg. Host1 and Host2 associated with TemplateX. they have 90% similar items/triggers. However the remaining 10% is somehow different (eg. they are required to be monitored for a different process)

TemplateX outlook:
90% same items applied to Host1 and Host2
monitor process[aaaaa] for Host1
monitor process[bbbbb] for Host2

Therefore user go manually to Host1 to DEACTIVATE [bbbbb]
Therefore user go manually to Host2 to DEACTIVATE [aaaaa]

Here is the problem,
whenever user attempts to UPDATE aaaaa or bbbbb in the TemplateX, the 'updated' items will cause items [aaaaa bbbbb] in Host1 and Host2 to be ACTIVATED again causing false triggers (because process bbbbb does not exists in Host1 and vice versa).

Question: should Zabbix store the "Activate OR Deactivated" in somewhere before user attempts to update the templateX and the status to remain SAME even AFTER for eg. (user changes the item interval or item name etc)

[Alexei]

I already see some other ZABBIX user crying "I want to active all items of all hosts by one-click on a template. Why I cannot do it?" Both update methods must be supported somehow.

[BusteR81]

yah

I personally agree with you

that i need hosts to rememb their own item/trigger status so that while updating template, their ACTIVATE or DEACTIVATE will not change

BUT others

wan a 1 click button to on all items/triggers to hosts associated to template

Therefore i suggest zabbix developers throw in a check box below like:
-
| | Check box to update status as per this Template
_

If user does not check the box, then all items/triggers status will be UNchanged but changes such as item names, time interval, custom multiplier etc will still be apply and updated.

[Andreas Bollhalder]

I have reported this too here

Andreas

[BusteR81]

yah

I have reported this too here

Andreas

i juz read your post. same problem as me. anyway lets hope the next zabbix ver have such function for users like us who relies alot on templates.

Cheers

[Alexei]

This will be implemented in one of 1.4.x.