An operations team is establishing a baseline observability architecture for a hybrid application running on Compute Engine instances and on-premises servers. The team must collect system metrics and log data, centralize observability in Google Cloud, and optimize storage costs by preventing low-severity debug logs from being ingested into log buckets, while maintaining strict access controls. Which TWO actions should the team take to meet these requirements?
- Install and configure the Google Cloud Ops Agent on Compute Engine instances to collect system metrics and application logs.Answer
- Configure a Cloud Logging Log Router exclusion filter to prevent log entries with severity levels below INFO (such as DEBUG) from being ingested into log buckets.Answer
- CCreate an aggregate exclusion filter targeting all log entries with severity ERROR and CRITICAL to minimize overall log ingestion volume.
- DGrant the primitive Owner role (roles/owner) to the Ops Agent service account to ensure unimpeded access to telemetry write endpoints.
- ERely strictly on IAM permissions assigned to Log Buckets to block unauthorized log data exfiltration across project perimeters without configuring VPC Service Controls.
Answer
The correct actions are installing the Google Cloud Ops Agent on Compute Engine instances and configuring a Cloud Logging Log Router exclusion filter for severity levels below INFO.
Installing the Google Cloud Ops Agent provides comprehensive metric and log telemetry collection for VM instances. Setting up a Log Router exclusion filter for log severities below INFO prevents excessive storage consumption by filtering out verbose debug messages before ingestion.
Step-by-Step Solution
Key Concept
Monitoring, Logging, and Observability Integration