Logging & Monitoring in Microservices

We will discuss one of the most important aspects of the Microservices system, which is the logging and monitoring. Without proper logging and monitoring, we are going to have a lot of problems with our system. It might lead to its failure too.

As I said earlier, this is extremely important in Microservices projects even more than monolith. The reason for that is that in Microservices, the flow goes through multiple processes. In this case its difficult to get holistic view of the system or entire flow. Most of the time in traditional monolith, we can examine logs and see what went wrong or what is happening. In this case with Microservices, it is difficult to stitch things together as it involve many processes.

We can look at a specific service and understand if there are any problems with it. Its very difficult to figure out what is going on with all the services working together. All these problems are handled by well-designed logging and monitoring.

Logging vs Monitoring

These two terms are often used interchangeably. Whats the difference between the two?

Logging

1. Recording the system’s activity. We document what the system did and what the users did and how did the system behave etc.. This is useful for analyzing the system’s behavior and making sure everything is good.
2. Auditing -We can see users behavior and see what they did.
3. Documenting errors…