Stringify sidekiq job args in logs
What does this MR do?
If these logs are sent to Elasticsearch, it will not be able to process nested object fields, as this causes a type mismatch with scalar elements in the same array across log lines.
This is a second attempt, as the first (reverted) one modified the actual job object that was used by sidekiq.
Related: https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8931
2nd attempt at: !26075 (merged)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team