Microservices are great. They are easily deployable, scalable and by definition, they are small, flexible and many. However, one big challenge in a microservices tech estate is understanding cause and effect. How to track various code releases, happening multiple times a day, pushed by various different teams in a completely random order, which may break another service or a business function was a real challenge at the FT. I will talk about our journey from manually creating Change Requests to an integrated, automated change log process. Along with some unexpected ways we ended up using this data, I will cover the tools and methods we used to get it adopted across engineering.