Question

Difficulty: EasyMonitoring and Logging

An operations team needs to collect system metrics (such as memory utilization) and application log files from a fleet of Compute Engine Virtual Machine (VM) instances. Which of the following actions should the team perform following Google Cloud recommended practices? (Select TWO.)

  1. Install the unified Google Cloud Ops Agent on each Compute Engine VM instance.Answer
  2. Configure the Ops Agent configuration file (config.yaml) to specify custom log receivers and metric pipelines.Answer
  3. C
    Install both the standalone legacy Stackdriver Monitoring Agent and legacy Stackdriver Logging Agent on each VM instance.
  4. D
    Assign the Owner primitive IAM role to the VM service account to grant necessary telemetry writing permissions.

Answer

To collect system metrics and log files from Compute Engine VMs following Google Cloud recommended practices, the team should install the unified Google Cloud Ops Agent on each instance and configure the agent's config.yaml file to define the required log and metric pipelines.
Google Cloud recommends installing the unified Google Cloud Ops Agent on Compute Engine instances to gather telemetry such as memory usage, disk metrics, and system logs. Custom log paths and metric ingestion settings are configured directly in the Ops Agent's config.yaml file.

Step-by-Step Solution

1
Identify the recommended telemetry agent for Compute Engine VMs
Recognize that the Google Cloud Ops Agent combines logging and monitoring into a single unified agent.
Google Cloud recommends the Ops Agent over legacy Stackdriver agents for all new Compute Engine observability setups.
2
Determine agent configuration procedure
Identify that configuring /etc/google-cloud-ops-agent/config.yaml allows custom log paths and system metric gathering.
The unified agent uses a YAML file to customize logging receivers and metrics pipelines.

Key Concept

Google Cloud Ops Agent deployment and configuration for Compute Engine telemetry
Rate this question