You recently deployed a Go application on Google Kubernetes Engine (GKE). The operations team has noticed that the application's CPU usage is high even when there is low production traffic. The operat

Question

Options

• ADeploy a Fluent Bit daemonset on the GKE cluster to log data in Cloud Logging. Analyze the logs
• BCreate a custom dashboard in Cloud Monitoring to evaluate the CPU performance metrics of your
• CConnect to your GKE nodes using SSH. Run the top command on the shell to extract the CPU
• DModify your Go application to capture profiling data. Analyze the CPU metrics of your application

• A
  8% (3)
• B
  15% (6)
• C
  5% (2)
• D
  73% (29)

Explanation

Go has built-in pprof profiling support. By instrumenting the application to expose profiling data (via net/http/pprof or the Cloud Profiler Go agent), Cloud Profiler can continuously collect CPU profiles and display a flame graph that shows exactly which functions and call paths consume the most CPU - down to individual function names. This gives actionable, function-level visibility. Fluent Bit and Cloud Logging (A) capture log lines, not CPU call stacks. A Cloud Monitoring dashboard (B) shows aggregate node/container CPU metrics but cannot attribute usage to specific Go functions. The top command over SSH (C) shows process-level CPU for the entire container, not individual function breakdowns.

No community discussion yet for this question.