News for hackers. Stuff that matters.
Re:AWS CodeDeploy by mwarkentin on Wednesday November 12, 2014 @03:31PM (#8597936)
Have you written anywhere how you guys deal with operational monitoring (eg. Boundary, New Relic, etc.) when you're spinning up brand new instances all of the time?
Re:AWS CodeDeploy by fmotlik on Wednesday November 12, 2014 @04:22PM (#8598278)
A bit: http://blog.codeship.com/lxc-memory-limit/

We use librato for monitoring our build server infrastructure and mostly only look at max/min values for metrics that could mean trouble. Generally we're able to separate data of different instances by their instance id so we could look into them individually.

We use NewRelic for our Rails application on Heroku and pump Heroku data into Librato as well (we love data and metrics)

And of course you can always send me an email to [email protected] with questions.

Re:AWS CodeDeploy by dk8996 on Wednesday November 12, 2014 @05:15PM (#8598622)
I have used Stackdriver (http://www.stackdriver.com/) before and it works good. It can get a bit pricey. They got bought by Google few months ago -- something to watch out for. I really had a good exp with their product.
Re:AWS CodeDeploy by samstave on Wednesday November 12, 2014 @05:48PM (#8598789)
We use stackdriver very heavily - but also take a look at SignalFuse.