Limit user information to RackAttack throttles
What does this MR do?
While browsing the auth.log on Kibana, I noticed that on Rack Attack blocks events we're not filling the Rack Attack discriminator, so user_id appears as nil on these cases. This MR limits the user info only to throttle_authenticated_api and throttle_authenticated_web.
Rack Attack log example: https://log.gitlab.net/goto/e4b7365fc2be37fc5b61d24c1d94dbce
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation created/updated or follow-up review issue created
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Related to #62756 (moved)
Edited by 🤖 GitLab Bot 🤖