Zabbix server 5.0.4
AWS EC2 instance running Windows OS with agent installed. Agent works as expected when instance is running.
We have several EC2 instances that are not running continuously. Dev ops turns them on and off as necessary. When they are in instance stats "stopped" we are alerted that the Zabbix agent is unreachable. Since we monitor Zabbix and not AWS this causes incidents to investigate why the agent isn't running and basically wastes time.
The basic config is {HOSTNAME:agent.ping.nodata(30m)}=1
Is there an expression to add to the trigger that checks the EC2 instance and if found to be stopped, to ignore the 2nd expression or at least notify that instance is stopped?
Thanks.
AWS EC2 instance running Windows OS with agent installed. Agent works as expected when instance is running.
We have several EC2 instances that are not running continuously. Dev ops turns them on and off as necessary. When they are in instance stats "stopped" we are alerted that the Zabbix agent is unreachable. Since we monitor Zabbix and not AWS this causes incidents to investigate why the agent isn't running and basically wastes time.
The basic config is {HOSTNAME:agent.ping.nodata(30m)}=1
Is there an expression to add to the trigger that checks the EC2 instance and if found to be stopped, to ignore the 2nd expression or at least notify that instance is stopped?
Thanks.