Answer-first summary for fast verification
Answer: Logs are excluded after they are received by the Logging API. Therefore, excluding logs does not reduce the number of entries.write API calls.
The correct answer highlights that the issue stems from the logs being processed by the Logging API before exclusion filters are applied, meaning the quota is still being impacted by the volume of logs initially sent. The solution involves reducing the logs collected at the source. Other options are incorrect because exclusion filters operate post-log submission to Cloud Logging, and no additional permissions are required for the Managed Instance Group to utilize these filters. For further details, refer to the documentation on logging quotas and exclusions.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Imagine you're a DevOps engineer at a rapidly growing social media company, responsible for monitoring their flagship web application. The application, deployed on Managed Instance Groups behind an HTTP(S) load balancer, is generating logs at such a volume that the project is exceeding the logging API quota. Despite implementing exclusion filters in Cloud Logging, the issue continues. What could be the underlying problem?
A
The exclusion filter was not configured properly.
B
More log types need to be added to the exclusion filters.
C
Logs are excluded after they are received by the Logging API. Therefore, excluding logs does not reduce the number of entries.write API calls.
D
The service account of the Managed Instance Group needs additional permissions to use the exclusion filters.
No comments yet.