Fix for sidekiq metrics set cardinality growing unbounded
What does this MR do?
It puts every event based legacy metric behind a feature flag toggle allowing enabling them one by one, or disabling them individually if their cardinality is too high.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Metrics labels contain user supplied data, this leads to cardinality explosion.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-qamanual pipeline job)
What are the relevant issue numbers?
Closes #43424 (closed)
Edited by Paweł Chojnacki