Microservices with Docker on Microsoft Azure™ (includes Content Update Program)

Monitoring Services

The last piece in the puzzle is monitoring the services themselves. Having good monitoring in place is important to keeping any application healthy and available. In a microservices architecture good monitoring is even more important. We not only need to be able to monitor what is going on inside a service, but also all the interactions between the services and the operations that span them. When an anomaly occurs, the inter-services information is much needed to understand the causality and find the root cause. It’s important to embrace the following design principles to achieve it.

• Log aggregation and analytics

• Use activity or correlation ID’s

• Consider an agent as an operations adapter

• Use a common log format