Microservices observability and performance management with Istio and Mixer Saying that developers are excited about Istio is a total understatement! Few technologies in the microservices and container space are getting as much attention as Istio, which IBM launched in May along with partners Google and Lyft. While microservices have become an increasingly common architecture for applications, managing and monitoring deployments can be tricky. Enter Istio and Mixer.

One of the most important benefits that Istio brings to microservices developers is observability. It was one of the most common keywords I heard repeated at KubeCon Austin presentations.  As users start to transition their applications from monolithic architectures to microservices, they often ask about how to get visibility into their deployed microservices beyond simple cpu and memory metrics. With Istio you get fine-grained detailed metrics such as:

  • Mesh Global Request Volume
  • Mesh Global Success Rate
  • Success Rate by Service
  • Response Time by Source and Version

At KubeCon, I had the pleasure to speak to Google Senior Software Engineer, Douglas Reid, about microservices observability with Istio and Mixer. In the video series below, we discuss the ease of activating tracing and observability in your microservices deployment with Istio, how Mixer acts as a plug-in framework to extract performance data (logs, metrics and traces) in your deployment, how Mixer will be used for service level performance and telemetry and finally how analytics and AI may be used in the future on traces and metrics. Check out the videos below and learn more at istio.io!

Observability in the Istio Service Mesh

Istio Mixer and Observability in Microservices

Roadmap for Service Level Metrics in Istio

Future of Observability in Istio – Analytics, AI and Alerts

2 comments on"Microservices observability and performance management with Istio and Mixer"

  1. Morning Lin,

    I am reaching you just for pointing out that the last video (Future of Observability in Istio – Analytics, AI and Alerts) doesn’t link to the proper one. It just links to the previous one (Roadmap for Service Level Metrics in Istio).

    Thanks for the blogpost and have a wonderful day!

Join The Discussion

Your email address will not be published. Required fields are marked *