Your company has an application deployed on Anthos clusters (formerly Anthos GKE) that is running multiple microservices. The cluster has both Anthos Service Mesh and Anthos Config Management configured. End users inform you that the application is responding very slowly. You want to identify the microservice that is causing the delay. What should you do?

The Service Mesh visualization in the Cloud Console, powered by Anthos Service Mesh, provides detailed telemetry, including latency, traffic, and error rates, for services within the mesh. This allows you to quickly identify which microservice is experiencing high latency and causing the overall application slowdown. Anthos Config Management (ACM) is for managing configurations across clusters, not for real-time performance monitoring. While you can use ACM to select clusters or namespaces, it won't provide the necessary performance metrics to diagnose latency issues. Reinstalling Istio is a disruptive operation and unnecessary, as Anthos Service Mesh (which includes Istio) already collects this telemetry.