Answer-first summary for fast verification
Answer: The custom Service Account lacks the necessary permissions.
FluentD is utilized for logging purposes, not for monitoring. The agent's operation is confirmed as it was mentioned to be installed and configured. The geographical location of the Compute Engine does not impact the monitoring workspace's functionality. The absence of metrics in the workspace could indeed stem from the custom Service Account not having sufficient permissions. For further details, refer to: https://cloud.google.com/monitoring/agent/monitoring/troubleshooting#verify-creds
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your company operates multiple Projects within its Google Cloud Organization hierarchy, with resources across these Projects configured to send metrics to a centralized monitoring workspace. Recently, you deployed Apache on a Compute Engine instance using a custom Service Account in one of the Projects. After installing and configuring the monitoring agent to collect metrics from the Apache application, you observe that no Apache metrics appear in the centralized monitoring workspace. What could be the reason for this issue?
A
The Compute Engine is located in a different region from the monitoring workspace.
B
The Fluentd agent was not installed correctly.
C
The custom Service Account lacks the necessary permissions.
D
The monitoring agent is not active on the Compute Engine instance.
No comments yet.