rm-tracker Decommission Q1 Checkpoint

Hello everyone :wave:

As most of you are aware of, last year @data-mlep announced that we will decommission rm-tracker this year. We also have encouraged all RMI users to migrate to use tracking v2 owned by the CDE team for better consolidating our tech stack in Data team. For more details on the reasoning why we decided to decommission this, you can refer to this doc.

Since we have entered Q2, we did a quick recap on the migration progress. Thanks to everyone’s effort, there are 10 out of 16 services (62.5%) that have been migrated to use tracking v2 :yay:

What to do

If you are the owner of these services:

eats-menu-tagging-serving
flight-passengers-model
fraud-bb-user
fraud-image-detection
mkt-coupon-abuse
r1-r2

Please help to:

Migrate your service to use tracking v2

Refer to this page on guideline to use tracking v2

After the migration is done, update the status in this spreadsheet to Done

Timeline

Nov 30, 2021: New services are not allowed to use rm-tracker
Jun 30, 2022: rm-tracker end of support
Dec 31, 2022: rm-tracker end of life
Jun 30, 2023: Data in rn-tracker BQ will be archived

Support

If you have any questions or need additional support to do the migration, you can mention @data-mlep in #rm-support.

Thank you :bows: