Please double check the configuration of triggers whether they are not using *.NAME macros. In such case the results are indeed misleading and displaying all contents matching the name criteria.

I have triggers like:
'DNS name was changed for {HOST.NAME}'

and I have noticed problem with Actions, where i try to set:

Trigger name like "DNS name" - it does not work

Is there any possibility to make that string working? Where I can find an information in zabbix documentation that 'name' should not be included in trigger searching?

Hello Lukas,

Could you please clarify - the condition with Trigger name like name doesn't work at all or working not as expected ? For example, Zabbix sends the notifications about the trigger which doesn't contains "name" string directly in the trigger name, but contains macro like {HOST.NAME}?

Regards,
Aleksejs!

Hello Aleksejs,

apologize for providing incomplete Information. When I set "DNS name" in the condition (Trigger name not like "DNS name"), zabbix still send me notifications about my triggers 'DNS name was changed for {HOST.NAME}'. So I checked if searching is properly in Monitoring -> Triggers. I put "DNS name" in Name and nothing happened. When I put only "DNS", strange but it worked.

Please check attachment, I took screenshots.

Regards, Lukasz

lukas.sz, normally searching for trigger with name 'DNS name', when you have a trigger with name that contains 'DNS name', you should be able to find it.
Can you, please, make sure that all the characters in both Trigger name (Configuration -> Hosts -> Triggers) and search string (Monitoring -> Triggers) are the same? We assume, you may have some different language characters or some other difference.

Hi Valdis,

Yeap, there was additional whitespace character, so after deleting them, searching is working now properly. I apologize for any inconvenience with this ticket, we can close it now.

Thanks and regards, Lukasz

aleksejs.petrovs, about searching within entries with unexpanded macros, we agree, that it may be more continent to search within expanded trigger name.
But as for current implementation, adding search within trigger name with expanded macros will require switching from SQL search to requesting and expanding all triggers and searching within them with PHP. The later will work much slower and on bigger systems will create performance issues. Sadly it was decided not to change it now.