Examkin

Question

Difficulty: MediumMonitoring and Logging

A cloud operations team recently deployed a set of database virtual machines on Compute Engine. While reviewing the Cloud Monitoring dashboard, they observe that hypervisor-level metrics like CPU utilization and network traffic are visible, but guest OS memory utilization and disk space usage metrics are unavailable. Which action should the team take to collect these missing metrics in accordance with Google-recommended practices?

  1. Install the Google Cloud Ops Agent on the virtual machine instances.Answer
  2. B
    Install the legacy Stackdriver Monitoring agent on the virtual machine instances.
  3. C
    Grant the primitive Owner role to the Compute Engine default service account.
  4. D
    Enable the Cloud Monitoring API at the Organization resource node level.

Answer

Install the Google Cloud Ops Agent on the virtual machine instances.
Compute Engine hypervisors natively collect host-level metrics like CPU utilization and network I/O. However, memory utilization and guest file system usage are internal to the operating system. Installing the Google Cloud Ops Agent inside the VM instance captures these guest OS metrics and transfers them to Cloud Monitoring according to Google-recommended practices.

Step-by-Step Solution

1
Identify the missing telemetry types.
Memory utilization and disk space usage are guest operating system level metrics, whereas CPU utilization is provided by default by the Compute Engine hypervisor.
Hypervisors cannot view internal OS memory allocation without in-guest software.
2
Select the current Google-recommended telemetry collection software.
The Google Cloud Ops Agent is the primary unified agent for collecting metrics, logs, and traces from Compute Engine instances.
Legacy Stackdriver agents are deprecated in favor of the unified Ops Agent.

Key Concept

Google Cloud Ops Agent vs. Hypervisor Metrics
Estimated Time:1m 30s
Rate this question

Topics

Monitoring and Logging

More questions from this topic