QuestionQ308

Ensuring solution and operations excellence

You have an application running in Google Kubernetes Engine (GKE). During the past 2 weeks, customers have reported that a particular part of the application returns errors very frequently. No logging or monitoring solution is currently enabled on the GKE cluster. You want to diagnose the issue, but have been unable to reproduce it. You want to minimize disruption to the application. What should you do?

  • A
    1. Update your GKE cluster to use Cloud Operations for GKE. 2. Use the GKE Monitoring dashboard to investigate logs from affected Pods.
  • B
    1. Create a new GKE cluster with Cloud Operations for GKE enabled. 2. Migrate the affected Pods to the new cluster, and redirect traffic for those Pods to the new cluster. 3. Use the GKE Monitoring dashboard to investigate logs from affected Pods.
  • C
    1. Update your GKE cluster to use Cloud Operations for GKE, and deploy Prometheus. 2. Set an alert to trigger whenever the application returns an error.
  • D
    1. Create a new GKE cluster with Cloud Operations for GKE enabled, and deploy Prometheus. 2. Migrate the affected Pods to the new cluster, and redirect traffic for those Pods to the new cluster. 3. Set an alert to trigger whenever the application returns an error.
Explanation

Enabling Cloud Operations for the existing GKE cluster provides workload logging and monitoring without migrating Pods or redirecting production traffic. Workload logs can be examined for the affected Pods to diagnose intermittent customer-facing errors. Creating a replacement cluster is unnecessary disruption, while deploying Prometheus and setting an alert primarily supports future detection rather than investigating the observed errors.

Learn more

Community Discussion

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