An enterprise organization operates hybrid workloads across Compute Engine virtual machines and Google Kubernetes Engine (GKE) clusters. The operations team requires a centralized observability architecture that retains application and system logs for seven years to meet regulatory compliance while enabling real-time alerting for operational anomalies. The architecture must ensure that high-severity logs and security audit trails are guaranteed to be ingested without loss. Which TWO architectural actions should the team implement to fulfill these requirements?
- Configure an organization-level aggregated Log Router sink to stream all audit and application logs to a Cloud Storage bucket for long-term compliance storage.Answer
- Deploy the Google Cloud Ops Agent on Compute Engine instances and enable native GKE system logging to collect operational metrics and telemetry for real-time Cloud Monitoring alerting.Answer
- CApply a broad Log Router exclusion filter matching `severity >= ERROR` across all project log buckets to lower overall Cloud Logging storage costs.
- DGrant the primitive Owner role (`roles/owner`) to the Log Router sink writer identity on the destination storage sink to ensure uninterrupted log delivery.
- ERely solely on Cloud IAM bucket roles without configuring VPC Service Controls perimeters around the central log storage repository.
Answer
The recommended actions are to configure an organization-level Log Router sink pointing to Cloud Storage for compliance retention and to deploy the Ops Agent alongside GKE logging for real-time observability.
Centralized observability for hybrid GCP workloads requires capturing operational telemetry via the Ops Agent on Compute Engine and GKE integrated logging, alongside using an organization-level Log Router aggregated sink to route compliance logs into long-term Cloud Storage buckets.
Step-by-Step Solution
Key Concept
Centralized Log Aggregation and Observability Integration