Skip to content

Update log data for NewAbuseReportWorker

Ian Anderson requested to merge abuse-report-worker-logging into master

What does this MR do and why?

Related to: https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/614

The log messages were not appearing in elastic when the NewAbuseReportWorker. I think that this may be due to attempting to assign a value to what elastic already sees as a nested key (json.user). When running in GDK logs are emitted in application_json.log as expected so something is happening in the parsing.

Even if this does not fix the issue, it will at least align the logging fields for what is expected by using json.username and json.user_id instead of json.user.

Additionally, this MR adds more clarity to the reason when a user is banned.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports