Best practice, different alarms on items compared to their templates

[vanessa]

Looking at ways to control what and when individual items should alarm for individual hosts.

I was thinking about adding tags to individual items, such as "24/7", to determine whether they should notify 24/7. But if you modify the template or the template "re-sync", then these tags are lost (so they aren't guaranteed to be persistent). It's natural to want the hosts to be synced with their templates (to not clone the items, unlink the template and what not).

So what are my options here? Is there a smooth and sustainable way to do this? I have about 100 hosts of various types (but mostly using the same few templates) which change their alarm specifications sometimes.

[cyber]

Can you elaborate a bit, where and how did you add those tags? Directly on a host, modifying an item? Then I would understand them dissappearing after template updates...
Its not so straightforward to make one item/trigger behave differently in different hosts.. specially, if you want each of them to be individually tunable. You can add tags to a host directly, they would affect all events from that host. You could modify triggers to have usermacros and define those on host level, but that either affects all at once or you need a lot of macros to define behaviour of each trigger ..