Answer-first summary for fast verification
Answer: Adjust the alerting policy's Group By field to include namespace, cluster, and location for precise incident identification.
Option C is the correct choice as it involves the least operational overhead by simply updating the alerting policy to include additional grouping criteria (namespace, cluster, and location), thereby enabling unique identification of incidents. Options A and B, while potentially effective, introduce unnecessary operational complexity by requiring service renaming or additional workspace management. Option D is less optimal due to the significant operational overhead and potential lack of resolution if service names remain identical. Reference: [Google Cloud Documentation](https://cloud.google.com/stackdriver/docs/solutions/gke/troubleshooting#alerting).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your company manages three distinct environments: production, staging, and development, each with its own GCP Project. Additionally, there's a monitoring project featuring two workspaces—one dedicated to production and the other shared between development and staging. A GKE Cluster is operational in both staging and development environments for testing an application before its production deployment. Both clusters host a service named 'app-serve', and an alerting policy monitors this service within the workspace. However, incidents on the service cannot be uniquely attributed to either the development or staging service in the GKE monitoring dashboard. What is the most efficient solution to this issue with minimal operational overhead?
A
Modify the service name in one of the clusters to distinguish between environments.
B
Establish a separate workspace for the development environment to isolate its monitoring.
C
Adjust the alerting policy's Group By field to include namespace, cluster, and location for precise incident identification.
D
Rename one of the clusters to ensure unique identification of services across environments.
No comments yet.