An organization operates three separate Google Cloud projects (`proj-services-prod`, `proj-data-prod`, and `proj-auth-prod`) hosting microservice workloads. The Operations team needs a single, centralized Cloud Monitoring dashboard and alerting view to monitor compute infrastructure metrics across all three projects simultaneously without moving the workloads. They create a central administrative project named `proj-monitoring-central`. Which step should the Cloud Engineer perform to achieve this unified observability setup?
- Add `proj-services-prod`, `proj-data-prod`, and `proj-auth-prod` as monitored projects within the Metrics Scope of `proj-monitoring-central`.Cevap
- BGrant the primitive Owner role (`roles/owner`) on `proj-monitoring-central` to the default Compute Engine service accounts of all three production projects.
- CInstall the legacy Stackdriver Monitoring agent on all virtual machines and hardcode the project ID `proj-monitoring-central` in the legacy agent configuration file.
- DConfigure Organization Policies at the root organization node to force telemetry data inheritance down to `proj-monitoring-central`.
Cevap
Add `proj-services-prod`, `proj-data-prod`, and `proj-auth-prod` as monitored projects within the Metrics Scope of `proj-monitoring-central`.
Google Cloud Monitoring uses Metrics Scopes to consolidate observability across multiple projects. By designating `proj-monitoring-central` as the scoping project and adding `proj-services-prod`, `proj-data-prod`, and `proj-auth-prod` as monitored projects within its Metrics Scope, operations teams can view unified dashboards, query combined metrics, and set up centralized alerts across the entire fleet without modifying individual workloads.
Adım Adım Çözüm
Anahtar Kavram
Cloud Monitoring Metrics Scope (Multi-Project Monitoring)
Tahmini Süre:2m 0s