We host our servers in AWS as EC2 instances. One of the benefits of this is that you can quickly spin up clones of various servers but I'm encountering a problem with Zabbix when I launch new instances.
I have Zabbix set up to monitor the log files on several of our servers. When I clone an instance in AWS the cloned instance will automatically reprocess the log file and send its alerts to the Zabbix Host set up for the original server causing a bunch of false positives and a ton of alerts clogging up e-mail. It also seems to keep the original server from sending its log information to zabbix breaking monitoring on the original server.
Here is what happens broken down into steps:
Step 1 - make a clone server_1 who's hostname is server_1 and ip is 10.1.1.1
Step 2 - launch clone
Step 3 - clone boots with a hostname of server_1 and an ip of 10.1.1.2
Step 4 - clone starts processing the log file from the beginning and sends its data to the zabbix host set up for the original server.
Is this supposed to happen and is there a way I can keep this from happening?
I'd like the new clone to not send zabbix any information until I have set up the host in Zabbix Server.
I had assumed that even if the hostnames were the same b/c the ip's were different and the new host hadn't been set up in zabbix it wouldn't send any info back to the zabbix server but obviously this ins't the case.
Thanks for any help you guys can provide!
**Note: I'm using Zabbix 1.8.11
I have Zabbix set up to monitor the log files on several of our servers. When I clone an instance in AWS the cloned instance will automatically reprocess the log file and send its alerts to the Zabbix Host set up for the original server causing a bunch of false positives and a ton of alerts clogging up e-mail. It also seems to keep the original server from sending its log information to zabbix breaking monitoring on the original server.
Here is what happens broken down into steps:
Step 1 - make a clone server_1 who's hostname is server_1 and ip is 10.1.1.1
Step 2 - launch clone
Step 3 - clone boots with a hostname of server_1 and an ip of 10.1.1.2
Step 4 - clone starts processing the log file from the beginning and sends its data to the zabbix host set up for the original server.
Is this supposed to happen and is there a way I can keep this from happening?
I'd like the new clone to not send zabbix any information until I have set up the host in Zabbix Server.
I had assumed that even if the hostnames were the same b/c the ip's were different and the new host hadn't been set up in zabbix it wouldn't send any info back to the zabbix server but obviously this ins't the case.
Thanks for any help you guys can provide!
**Note: I'm using Zabbix 1.8.11