One of the advantage of deploying a microservice-based application in an Istio service mesh is to allow one to externally control service monitoring, tracing, request (version) routing, resiliency testing, security and policy enforcement, etc., in a consistent way across those services, for the application as a whole. In this blog we will focus on the in-depth telemetry side of the house and see how can we configure mixer to collect a uniform set of metrics across all services. At the end of this blog our goal will be to have a new metric and a new log stream enabled for calls to services within our mesh.
We are going to use the Bookinfo application as an example.
Source: openshift.com