Microservices with Docker on Microsoft Azure™ (includes Content Update Program)
by Boris Scholl, Trent Swanson, Daniel Fernandez
Monitoring
Good monitoring 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’s going on inside a service, but also the interactions between the services and the operations that span them.
• Use activity or correlation IDs: These are used to associate events to a specific activity or transaction.
• Use a common log format: This enables better correlation of events across services and instances.
• Collect and analyze logs: By collecting logs from the various services and instances, we can analyze and query across multiple services and instances of a service.
• Consider using a sidecar: A sidecar is simply an out-of-process ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access