Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
Your company operates in production, staging, and development environments, each with its own GCP Project. A monitoring project includes two workspaces: one for production and another for development and staging. You've set up a GKE Cluster in both staging and development to test an application before its production deployment. Both clusters host a service named 'app-serve', and an alerting policy monitors this service in the workspace. However, incidents on the service cannot be uniquely associated with either the development or staging service in the GKE monitoring dashboard. What is the most efficient solution to this issue with minimal operational overhead?
Explanation:
The correct answer is to update the Group By field in the alerting policy by adding namespace, cluster, and location. This approach requires the least operational overhead and effectively differentiates between incidents in the development and staging environments. Other options, such as creating a separate workspace or renaming services or clusters, involve more significant operational changes and may not directly address the issue of incident association. For more details, refer to the documentation on why incidents might not be matched to a GKE resource.