[v24.3.x] kafka: add dedicated logger for authz failures #24718
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We currently log authz failures to the kafka log at info level, this means we have per request possible log spam with no fine grained control for them. Rate limiting does not quite do the thing we want, rate limiting would give us rate limiting at a global level, and what you would want is a rate limit per principal or maybe per (principal, resource). The simpler solution is to move the authz log to a dedicated logger so that it can be controlled seperately, or temporarily disabled/enabled for debugging. Fixes: CORE-8666 (cherry picked from commit 459ef48)
rockwotj
approved these changes
Jan 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of PR #24712