12 Using logs and traces to understand behavior
This chapter covers
- Storing logs in a consistent and structured way in a machine-readable format
- Setting up a logging infrastructure
- Using traces and correlation IDs to understand system behavior
In the previous chapter, we focused on emitting metrics from your services and using those metrics to create dashboards and alerts. Metrics and alerts are only one part of what you need to achieve observability in your microservice architecture. In this chapter, we’ll focus on collecting logs and making sure you’re able to trace the interactions between services. This will allow you to not only have an overview of how the system behaves but also go back in time and retrospectively follow each request. ...
Get Microservices in Action now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
