{HOST.NAME} macro in trigger names

[Engraf]

Good day!

In standard templates, trigger name may include the {HOST.NAME} macro or may not. So when I use notification with subject like "{EVENT.STATUS}: {HOST.NAME}: {TRIGGER.NAME}" (for example) then some times it looks normal but other times it looks like tautology .

If I'm not alone considering this an inconvenience, I think it would be good to correct this in future versions.

[kloczek]

In standard templates, trigger name may include the {HOST.NAME} macro or may not. So when I use notification with subject like "{EVENT.STATUS}: {HOST.NAME}: {TRIGGER.NAME}" (for example) then some times it looks normal but other times it looks like tautology .

Using {HOSTNAME} in trigger names always is tautology
If you will be forming message body or subject you can use this macro in message template despite what it is in trigger name.
In active triggers names lists in web frontend already it is separated column with host name so repeating second time such host name in whole table line makes such table less readable.
This why I'm not using such macros in my own templates https://github.com/kloczek/zabbix-te...and-guidelines