:fire: [Breaking Changes] Inventorizing Tracking Events:fire:

Background

We have 1573 registered tracking events in nrt-schema and Data Ops Platform v2. Some of the events are not being used or don’t have traffic, but they cost us in some ways, e.g. active streaming Dataflow jobs.

We are currently inventorizing and housekeeping the tracking events to identify which events that are not being used (so we can delete them) and who are responsible for the events.

What you need to do?

Our first step is identifying the Product Domains of the events. We have collected the list of tracking events that we have.

https://docs.google.com/spreadsheets/d/1_JI7B5ElgTkdoDKHi9xJVfCFLonATuaazIOLHW3Mxuk/edit

If you know what is the Product Domain of the events, select the product domain from the drop down.
If you don’t know the Product Domain but you know who might know, please comment on the cell mentioning their names.
If you know about the events and they are not used anymore, you can let the Product Domain empty, we will delete it later.

Deadline

We will lock the sheet on 31 March 2021, 5 PM UTC+7, then delete tracking events that don’t have Product Domain on ~~1 April 2021, 10 AM UTC+7~~ 5 April 2021, 10 AM UTC+7 :fire: (avoiding long weekend 2-4 April 2021)

This is really a collaborative effort, so we need your help and feedback.

Our next step would be identifying the people who are the “maintainer” of the events.

P.S.

Product Domain is concept established by Traveloka central engineering team to provide clear domain, responsibility, and cost allocation. See more here.
More information about the Product Domain list here.