Log write_count keys for each database config types
What does this MR do and why?
This MR tracks :write_count metrics and log keys per database. It adds db_primary_write_count and db_<main/ci>_write_count to the logs. We already track total db counts and cached counts. This allows us to track write counts per database.
Looking at gitlab-com/gl-infra/scalability#3771 (comment 2074687023), that would help us identify Sidekiq workers which are read or write-skewed on a database. That would empower devs to set data consistency more accurately.
Follow-up: open MR on runbooks index
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.