Change Details

**User story** As an engineer, I want aliases to have a dedicated and granular usage tracking key, especially in different languages (e.g., A.en, A.fr), so that alias changes are tracked per language and reduce irrelevant noise in the DB and watchlist. **Background** Alias changes are ~20% of all change propagation Currently, they are all in the O usage, which can’t be scoped Currently rated as an M ticket **Acceptance Criteria** [] Implement alias usage tracking with A.<lang> keys [] Ensure that the languages in the tracking are correct. [] Ensure other usages still work as usual [] Ensure that alias updates no longer cause noise in unrelated languages’ watchlists [] Set up collapsing limit configuration for aliases.

**User story** As an engineer, I want aliases to have a dedicated and granular usage tracking key, especially in different languages (e.g., A.en, A.fr), so that alias changes are tracked per language and reduce irrelevant noise in the DB and watchlist. **Background** Alias changes are ~20% of all change propagation Currently, they are all in the O usage, which can’t be scoped Currently rated as an M ticket How labels previously have been granularized . https://phabricator.wikimedia.org/T172914 https://phabricator.wikimedia.org/T90436 **Acceptance Criteria** [] Implement alias usage tracking with A.<lang> keys [] Ensure that the languages in the tracking in client are correct. Making sure wbc_entity_usage table had the correct language. [] Ensure other usages still work as usual, except O aspect [] Ensure that alias updates no longer cause noise in unrelated languages’ watchlists [] Set up collapsing limit (probably 10) configuration for aliases. **Success Metric** ~20% less changes are propagated.

**User story** As an engineer, I want aliases to have a dedicated and granular usage tracking key, especially in different languages (e.g., A.en, A.fr), so that alias changes are tracked per language and reduce irrelevant noise in the DB and watchlist. **Background** Alias changes are ~20% of all change propagation Currently, they are all in the O usage, which can’t be scoped Currently rated as an M ticket How labels previously have been granularized . https://phabricator.wikimedia.org/T172914 https://phabricator.wikimedia.org/T90436 **Acceptance Criteria** [] Implement alias usage tracking with A.<lang> keys [] Ensure that the languages in the tracking arin client are correct. Making sure wbc_entity_usage table had the correct language. [] Ensure other usages still work as usual, except O aspect [] Ensure that alias updates no longer cause noise in unrelated languages’ watchlists [] Set up collapsing limit (probably 10) configuration for aliasesses. **Success Metric** ~20% less changes are propagated.