Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ottomata | T185233 Modern Event Platform | |||
| Open | Ottomata | T238230 Decommission EventLogging backend components by migrating to MEP | |||
| Declined | None | T259734 BUOD-KR1-Q4+: Certify that analytics schema and instruments have been upgraded to use the MEP system (clearing the legacy system for sunsetting) | |||
| Open | Ottomata | T259163 Migrate legacy metawiki schemas to Event Platform | |||
| Resolved | mforns | T267333 Migrate Growth EventLogging schemas to Event Platform | |||
| Resolved | • Mholloway | T253121 MEP Client MediaWiki PHP | |||
| Resolved | Ottomata | T268517 Migrate Anti-Harassment EventLogging schemas to Event Platform | |||
| Duplicate | None | T267341 CookieBlock Event Platform Migration |
Event Timeline
@Niharika
Let us know if this schema needs client IP and/or geocoded data? If not, it will be removed as part of this migration.
Hi @Niharika I reached out to both of them and neither of them knew anything about this schema. According to meta.wikimedia.org history, you created and edited this schema in 2016 and 2017. It is marked as an Anti-Harassment team schema in our EventLogging Schema Audit spreadsheet. Is this incorrect?
That's correct. Sorry, I was looking at the wrong schema. This project was done as part of the Community Tech team's work back in the day when I was on that team.
Looking at the schema, it does seem like it captures the client IP to initiate a cookie-based block.
@Niharika: So, if I understand correctly, it should not be marked as Anti-Harassment, and it should be marked as Community Tech? If so, we can wait on responses from one of the team engineers who may know the background on it, such as @Samwilson or @MusikAnimal, although I see that Niharika also seems to have taken a look (and thanks for doing that!).
Ah, great, thank you!
- is the CookieBlock schema still used, and if not can we disable it altogether?
- If it is used, do you need the browser client's HTTP address and/or geocoded data of the client? I think this is different than the ip field in the CookieBlock schema, which looks like it is set directly by the instrumentation client code, correct? Data explicitly set by the client will not be changed, we're only trying to stop collecting client IP addresses of the event sender where we can.
@ifried I think it makes more sense for "cookie blocks" to be an Anti-Harassment project. It was taken on by Commtech as it was one of the earlier things that team was assigned, before AHT was even formed. It totally makes sense for AHT to maintain it though.
I will appreciate another look at the schema to make sure my comment is correct.
Ah, it looks like maybe @dbarratt originally marked this schema as Anti-Harassment. Maybe he knows more! :)
I propose we do not migrate this schema and mark it as unused. There hasn't been a schema edit on metawiki since Jan 2017, and there isn't even a Hive table for this, which means there hasn't been an event sent since before we migrated to Hive.