Question

A retail company runs dozens of microservices across several GKE clusters and Compute Engine instances, all managed by different teams under a single Google Cloud project. The SRE team wants a way to organize related resources so that dashboards, alerting policies, and health views can be scoped to specific applications (e.g., 'checkout', 'catalog') without manually listing every resource each time infrastructure is added or removed. New instances are created and destroyed frequently by autoscaling. What is the most operationally efficient approach in Cloud Monitoring?

Accepted Answer

Create Cloud Monitoring resource groups defined by dynamic membership criteria such as labels, tags, or naming patterns, then scope dashboards and alerts to those groups.

Answer

Manually add each resource to a static list in each dashboard and alerting policy, updating the list whenever autoscaling changes the fleet.

Answer

Export all metrics to BigQuery and build per-application views using scheduled queries that join on resource IDs.

Answer

Split each application into its own Google Cloud project so that monitoring is naturally scoped per project.