Professional Cloud ArchitectDemo

By Google · Question Mode

QuestionQ207

Ensuring solution and operations excellence

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

  • A Use the Service Mesh visualization in the Cloud Console to inspect the telemetry between the microservices.
  • B Use Anthos Config Management to create a ClusterSelector selecting the relevant cluster. On the Google Cloud Console page for Google Kubernetes Engine, view the Workloads and filter on the cluster. Inspect the configurations of the filtered workloads.
  • C Use Anthos Config Management to create a namespaceSelector selecting the relevant cluster namespace. On the Google Cloud Console page for Google Kubernetes Engine, visit the workloads and filter on the namespace. Inspect the configurations of the filtered workloads.
  • D Reinstall istio using the default istio profile in order to collect request latency. Evaluate the telemetry between the microservices in the Cloud Console.
Explanation

Anthos Service Mesh telemetry in the Google Cloud console provides service-level latency metrics, service-to-service traffic details, and a topology visualization. Inspecting that visualization and its communication-edge performance reveals the microservice responsible for elevated latency. Anthos Config Management is for managing configuration, not analyzing runtime service latency.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!