I got few zabbix trapper items that receive data every second.
If no triggers created - all is OK and data successfully pushed to db without lag
If I create nodata()=1 trigger for each one - all is OK and data successfully pushed to db without lag
If I create group trigger that must should appear if all items in group have no data for 1 minute - all item in group almost stop to go to DB, history cache start growing, lag for 'last data' for those items is growing. After history cache overloading - lost data.
So what is the problem and why it work in such way? How to make trigger for group of 50+ items if even 5 already cause lag history delivery
Group trigger example:
Zabbix 6.0.30
If no triggers created - all is OK and data successfully pushed to db without lag
If I create nodata()=1 trigger for each one - all is OK and data successfully pushed to db without lag
If I create group trigger that must should appear if all items in group have no data for 1 minute - all item in group almost stop to go to DB, history cache start growing, lag for 'last data' for those items is growing. After history cache overloading - lost data.
So what is the problem and why it work in such way? How to make trigger for group of 50+ items if even 5 already cause lag history delivery
Group trigger example:
Code:
nodata(/5413181cc5e2/acc180decf0f,1m)=1 and nodata(/5413181cc5e2/889e4b3d4225,1m)=1 and nodata(/5413181cc5e2/710d27574123,1m)=1 and nodata(/5413181cc5e2/6c93a2671fb4,1m)=1 and nodata(/5413181cc5e2/7f6d81bc66ae,1m)=1
Comment