|
I believe the decision to remove the prefix was hasty and did not consider its importance in service identification, such as for apache, php-fpm, etc. This change has resulted in all triggers appearing identical.
Regarding tags, they are primarily used to facilitate search, filtering, and indexing within Zabbix. For example, when filtering Apache triggers, tags are utilized rather than the trigger name. However, for clarity and visual identification and notification, the trigger must retain the prefix. Worrying about monitor resolution or trigger quantity is a mistake.
This mistake was mentioned before being removed, but they still decided to remove it.
In my opinion, please revert this change as soon as possible.
|
|
I'm glad they made the decision to roll back this feature so important on triggers prefix function... I was already thinking about how I was going to edit all my templates by putting a macro in each one in its place (yes, it works, but it's a workaround). If I update the template, I lose what I did. 
|
|
Today, I discover this bug... I cannot understand the first choice on https://support.zabbix.com/browse/ZBXNEXT-8746
We have lost important informations ! I understand for prefixes OS like "Linux:", where items name are uniques per host but it's a non-sense for applications templates where many template can by applied on one host ! Items, triggers have the same name !
Please revert this choice for all applications templates !
|
apache_http.png
