Monitoring the microservices

In the microservice architectural style, monitoring is a crucial part. There are a lot of benefits when we adopt this architecture, such as time to market, source maintenance, and an increase of business performance. This is because we can divide the business goals for different teams, and each team will be responsible for some microservices. Another important characteristic is optimization of computational resources, such as cloud computing costs.

As we know, there is no such thing as a free lunch, and this style brings some drawbacks, such as operational complexity. There are a lot of small services to monitor. There are potentially hundreds of different service instances.

We have implemented some of these services in our infrastructure but until now, we did not have the data to analyze our system health. In this section, we will explore our configured services.

Let's analyze right now!

Collecting metrics with Zipkin

We have configured our Zipkin server in the previous...