Over the 10 years of defined DevOps culture life we have gone a long road. We have been able to automate almost every step of the delivery process. But in my opinion, we still lack automated monitoring. The transition from the classic way of monitoring to Continuous Monitoring is hard. Not only because it demands very strict approach to the methodology, architecture, etc., but mainly because our organizational culture is not ready for it. The goal of the proposed talk is to create a common understanding of what Continuous Monitoring is, what foundations are needed to start building Continuous Monitoring, and what advantages the organizations will gain using it. I am going to go through defined principles, present the MEAL (Metrics, Events, Alerts and Logs), which is my approach to define the structure of Continuous Monitoring and, finally, discuss one of the complex tools to work with. I’d like to convince the attendees to audit and redefine their monitoring habits. Aimed with basic principles, the attendees will be able to define areas and best ways to design and implement Continuous Monitoring to their DevOps lifecycle.