fix: Logging SDK not applying quota limits for project set using quotaProjectId #1125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Customer uses google-cloud-logging SDK to fetch audit logs from their customers. Since they were facing lot of throttling error's because of the quota limitation's set at the service account, they decided to make use of the quotaProjectId field available while creating the Logging object (LoggingOptions Builder). But even after setting this field they see that quota is counted against the service account (Supplied via credentials) instead of the actual project for which call is being made.
The sample code used: