Checks, agregates and triggers.
Hi all !
I got some questions about triggers on agregated data.
I fact I got host groups with checks on a data without a trigger:
Check: misc[ipvs,{$HTTP_HOST1}] (this is a zabbix agent check with a script)
I got another group with host that are hosting agregated data from the other groups.
Check: grpsum["{$GRID_NAME}","misc[ipvs,{$HTTP_HOST1}]","last","0"]
Trigger: {Template_Grid:grpsum["{$GRID_NAME}","misc[ipvs,{$HTTP_HOST1}]","last","0"].max(3)}>1
The agregated data should not be different from 1, it a check on a Master IP that should be only mounted once on the Host Group.
If the IPVS is restarted or the IPVS master change, then the IP is mounted on another Host but the agregated value of the check can be more than 1 for a short period of time.
I want the trigger to not be activated each time there is an IPVS change.
I tried to use:
- .last(200,0)#1 to make it trigger after a period of time but didn't work.
- .min(3)#1 to try to avoid to much change but didn't work too
I'm starting to think it can be the grpsum that is not correct for our need ? Should I change the "last","0" of the Agregated trigger ?
If you have any idea I take it !
Thank you for your time.
I got some questions about triggers on agregated data.
I fact I got host groups with checks on a data without a trigger:
Check: misc[ipvs,{$HTTP_HOST1}] (this is a zabbix agent check with a script)
I got another group with host that are hosting agregated data from the other groups.
Check: grpsum["{$GRID_NAME}","misc[ipvs,{$HTTP_HOST1}]","last","0"]
Trigger: {Template_Grid:grpsum["{$GRID_NAME}","misc[ipvs,{$HTTP_HOST1}]","last","0"].max(3)}>1
The agregated data should not be different from 1, it a check on a Master IP that should be only mounted once on the Host Group.
If the IPVS is restarted or the IPVS master change, then the IP is mounted on another Host but the agregated value of the check can be more than 1 for a short period of time.
I want the trigger to not be activated each time there is an IPVS change.
I tried to use:
- .last(200,0)#1 to make it trigger after a period of time but didn't work.
- .min(3)#1 to try to avoid to much change but didn't work too
I'm starting to think it can be the grpsum that is not correct for our need ? Should I change the "last","0" of the Agregated trigger ?
If you have any idea I take it !
Thank you for your time.