Practical advice for monitoring microservices

Adrian McMichael explores property portal Rightmove's structured approach to logging and monitoring across more than 50 microservices, showing you how to get to the bottom of production issues and helping you drive improvement and a sense of ownership in your projects.

One of the benefits of a distributed microservices architecture is the potential to able to pinpoint issues with more accuracy. However, if logging is not treated like a first-class feature in your applications then you may find yourself unable to reason about the ways your well-planned systems are actually performing in the wild. Adrian McMichael explores property portal Rightmove’s structured approach to logging and monitoring across more than 50 microservices, showing you how to get to the bottom of production issues and helping you drive improvement and a sense of ownership in your projects. You’ll learn how building the right features into your logging, such as using a common specification for events, setting multidimensional metadata, standardizing event types, and designing for correlation, can be used to help diagnose issues and reason about the way your systems actually behave. You’ll also discover how practices like continuous delivery and monitoring reviews can help your teams understand and manage their applications more effectively, as you see how moving to containers with Docker has changed the way Rightmove monitors its system.