Nagios redundancy in AWS
Posted: Wed Sep 20, 2017 7:58 am
Has anyone successfully built instances of Nagios out in AWS that is effectively load balanced in a way that alerting is not duplicated?
What I would like to achieve is to have Nagios servers running in multiple availability zones within AWS to ensure monitoring functions as close to 100% of the time as possible. However, this presents challenges in some aspects of monitoring. For instance, if you have multiple instances of Nagios all polling for a specific device and that device goes down, you are going to get multiple alerts for that one incident. I think the inbound traps are easily solved with a load balancer but I dont know what it means for one of three Nagios servers to get a trap.
What are peoples thoughts on this design aspect?
What I would like to achieve is to have Nagios servers running in multiple availability zones within AWS to ensure monitoring functions as close to 100% of the time as possible. However, this presents challenges in some aspects of monitoring. For instance, if you have multiple instances of Nagios all polling for a specific device and that device goes down, you are going to get multiple alerts for that one incident. I think the inbound traps are easily solved with a load balancer but I dont know what it means for one of three Nagios servers to get a trap.
What are peoples thoughts on this design aspect?