Hi,
I'm doing A/B application deployments in EC2 so I am consistently deploying new app nodes in EC2. I use auto-registration so new nodes come up, puppet puts down the zabbix agent and config and they check in automatically to Zabbix server.
However since my trigger is {Template_Linux:agent.ping.nodata(300)}=1} so once the systems come up they alert PROBLEM then go to OK.
There has to be a creative way to make new nodes not alert and nodes that are really down to alert... I'm on Zabbix 2.x
I'm doing A/B application deployments in EC2 so I am consistently deploying new app nodes in EC2. I use auto-registration so new nodes come up, puppet puts down the zabbix agent and config and they check in automatically to Zabbix server.
However since my trigger is {Template_Linux:agent.ping.nodata(300)}=1} so once the systems come up they alert PROBLEM then go to OK.
There has to be a creative way to make new nodes not alert and nodes that are really down to alert... I'm on Zabbix 2.x
Comment