Trigger prototype with multiple items

[Ferke]

Hi,

I made a custom LLD about lost ping with 1 item prototype and 1 trigger prototype. Both work fine.
Currently if the ping is not working from the host to those items which have been discovered a trigger will be activated for every item. So I will have even 15 problem events which is bothering. Instead if all of them triggered I would like to see only one problem report, for example: "All client is not reachable"

Is it possible to create a such trigger prototype which can handle dinamically the different number of discovered items?

Thanks in advance!

[ovas]

Hello Ferke!

Have a look at the aggregated check item type: https://www.zabbix.com/documentation...ypes/aggregate
If you group all the discovered item hosts in one group and item keys are matching, you are free to collect aggregated data for all them as well as produce triggers for such aggregated checks.

[Ferke]

Hi,

Thanks for your reply, but it looks like this is not what I really want.

In my case there is only one host what I want to put in a trigger, but there are more (~10-15) items. The items are very similar to each other, for example:
For Host1:
Item1: fpinglost[10.11.12.164]
Item2: fpinglost[10.11.12.165]
Item3: fpinglost[10.11.12.166]
Item4: fpinglost[10.11.12.167]

For Host2:
Item1: fpinglost[10.11.13.100]
Item2: fpinglost[10.11.13.101]
Item3: fpinglost[10.11.13.102]

The fpinglost function gives me an integer from 0 to 3.

Because the itemkey is not the same, I think I cannot use the aggregate item.

I could make a trigger manually where I listed the items which are related to a certain host, but these items created by a LLD, so it would be great to generated automatically.

If you have any other idea, fill free to share with me.

Thanks!

[ovas]

In Zabbix 3.2, there is this event correlation feature that can close new/old events created by triggers based on Tag/Host group data. If you configure it the way for triggers to have some common tag data, you will be able to at least suppress the created events.

https://www.zabbix.com/documentation/3.2/manual/config/event_correlation