For the past two years my team and I worked with a large federal agency to deploy & migrate to a new container-as-a-service platform based on Docker. The migration has enabled development teams to isolate components of their code for faster, more reliable development. But, we also saw that the additional tooling - such as monitoring technology - supporting these services doesn’t yet map to the model that developers need to efficiently monitor their own services. In essence, the Develop->Test->Monitor loop is still broken for modern environments. So how do you fix it?

This presentation is based on my real-world experience with container platforms. Based on this work, I’ll address: How do you effectively instrument your systems, without pushing too much burden on to developers?How do you isolate data, dashboards, and alerts in a way that improves security while simplifying analysis? What can you do to give developers deep information when troubleshooting, without giving them the keys to the kingdom?How do you facilitate data-driven conversations among your developers and ops teams?

If you attend this talk, you’ll walk away with tested, practical ideas that will help your teams become more self-sufficient, improve data-driven conversations among your teams, and evolve your monitoring infrastructure to work more effectively with your CaaS platform.