We use Nagios and nrpe with a pretty standard monitoring setup. We also pull in cloudwatch data via python goto scripts.
As for the uptick I would avoid making any changes until after the AWS maintenance. We have also noticed an uptick in alerts,though not to that level. However just because your systems are not directly effected the increased activity due to others replacing systems, as well as what ever amazon is actually doing on the back end, means everyone will be effected to some extent. On Sep 28, 2014 11:06 AM, "Edward Ned Harvey (blu)" <b...@nedharvey.com> wrote: > > From: discuss-bounces+blu=nedharvey....@blu.org [mailto:discuss- > > bounces+blu=nedharvey....@blu.org] On Behalf Of Chuck Anderson > > > > Maybe this? > > https://aws.amazon.com/blogs/aws/ec2-maintenance-update/ > > I am aware of that - but they say less than 10% of their systems will be > affected, and "Customers who aren't sure if they are impacted should go to > the "Events" page on the EC2 console, which will list any pending instance > reboots for their AWS account." > > None of our systems are supposed to be impacted, and indeed, none of them > have been rebooting. > > The best I can tell, we're supposed to be unaffected, but the fragile > network is buckling and straining under the load, and causing rolling > network outages. > > I mentioned before, that during the last several months (May or so) we've > seen enormous variability in Amazon network performance... Sometimes you > download or upload a file and it goes 30Mbit/sec, sometimes 15KB/sec. And > it varies from minute to minute, hour to hour, day to day. > _______________________________________________ > Discuss mailing list > Discuss@blu.org > http://lists.blu.org/mailman/listinfo/discuss > _______________________________________________ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss