11
Logging and Monitoring
With a microservices solution, many services can interact with each other. When one service fails, the complete solution should not break. In the previous chapter, we covered different kinds of tests to find issues early. Here, we’ll look at finding issues in production as early as possible – probably before a user sees a problem.
To find issues when the application is running and see how the application runs successfully, the solution needs to be enhanced to offer telemetry data. With logging, we see what’s going on; based on different log levels, we can differentiate between informational logs and errors. With metrics data, we can monitor counters, such as memory and CPU consumption, and the number of HTTP requests. ...
Get Pragmatic Microservices with C# and Azure 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.
