Answer-first summary for fast verification
Answer: Logs are processed by the Logging API before exclusion filters are applied, meaning the API calls contributing to the quota are not reduced by filtering.
Options A and B are incorrect because exclusion filters operate after the logging API has been called, meaning the logs are already in Cloud Logging. Option C is also incorrect as adding more log types to the exclusion filters does not address the root issue. Option D is correct because the core issue lies in the entries.write API calls that push logs to Cloud Logging before exclusion filters can be applied. The solution involves reducing the volume of logs collected to prevent quota exceedance. There is no need for additional permissions for the Managed Instance Group's service account, as it already has access to Cloud Logging. For more information, refer to Google Cloud's documentation on logging exclusions and quotas.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a DevOps engineer for a rapidly growing social media company, you're part of the monitoring team for their flagship web application. The application, deployed on Managed Instance Groups behind an HTTP(S) load balancer, is generating logs at a volume that exceeds the Project's logging API quota. Despite implementing exclusion filters in Cloud Logging, the issue persists. What could be the underlying problem?
A
The Managed Instance Group's service account lacks the necessary permissions to utilize the exclusion filters effectively.
B
Exclusion filters are misconfigured, failing to reduce the log volume as intended.
C
Additional log types need to be specified in the exclusion filters to address the quota exceedance.
D
Logs are processed by the Logging API before exclusion filters are applied, meaning the API calls contributing to the quota are not reduced by filtering.
No comments yet.