How to do MonitoringAlertingLogging That Won’t Make Your Engineers Give Up

 

DevOps | Monitoring | Logging | Cloud Automation | Alerting | DevOpsDays

One of great things about Cloudify is that many of us working here have previously worked as production engineers before, and we apply the same principles that made us good engineers there, into making a better product here, which is intended for the users we used to be.

MonitoringAlertingLogging (which I personally feel have become so intertwined that it is difficult to discuss one without going into another) is one of those disciplines that I personally feel strongly about, so I decided to give a talk about it.



Changing the face of DevOps, Cloudify glues it all together. Download Free.  Go


So, I recently had the pleasure of speaking and participating in Baltic Devops 2016 in Tallinn, Estonia. Everything worked great from the moment I got off the plane to the point where I got back on 2 days later, and the overall conference (and city experience) was great.

The title of the talk was: “How to do monitoringalertinglogging that won’t make your engineers give up”.

The basic premise is: The ways bad monitoring/alerting/logging policies made me frustrated with jobs I’ve had. How to avoid these exact pitfalls and make your system friendly and keep your engineers happy.

The gist is:

  • Engineers are people just like everyone else
  • Keeping them happy is in your best interest
  • Here are the most common pitfalls and how to try to avoid them

Keep in mind, not all solutions are right for everyone, and like all things in life, you kind of have to try and see what works for you.

Slide deck: https://t.co/pidvdNmS5O

Video:

 



Leave a Reply