Page MenuHomePhabricator

Determine which remaining legacy EventLogging schemas need to be migrated or decommissioned
Closed, ResolvedPublic

Description

We're tracking EventLogging legacy schema migrations to Event Platform in the EventLogging Schema Audit spreadsheet.

We've still got 40+ schemas for which we don't know if we can decommission or have to migrate them. Most of them are inactive and/or old. ~20 of them don't have any results in codesearch; I'll assume that these can be decommissioned but will still list them here for reference. For the others, I'm going to follow up here (and elsewhere if needed) to try and find owners/deciders. I'll then update the audit spreadsheet with results.

This ticket is just about tracking down schema owners and making decisions. Any migrations will be tracked in separate tasks.

SchemaMigrate or Decom?Owners?codesearch results?

Related Objects

StatusSubtypeAssignedTask
ResolvedOttomata
OpenOttomata
DeclinedNone
OpenOttomata
ResolvedOttomata
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
ResolvedPginer-WMF
Resolvedphuedx
ResolvedMMiller_WMF
Resolvedphuedx
Resolvedphuedx
OpenNone
Resolvedphuedx
Resolvedphuedx
OpenNone
ResolvedEtonkovidova
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
OpenNone
OpenNone
Resolvedphuedx
Resolvedphuedx
Resolvedmatmarex
DeclinedNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Updated the description to reflect that the ExternalGuidance stream should be decommissioned.

(Also, sorry, Yuvi—I removed your username from the description, so you should be safe from this task now 😊)

Ottomata updated the task description. (Show Details)
Ottomata updated the task description. (Show Details)
Ottomata added a subscriber: nshahquinn-wmf.

Edited task to only include schemas we don't yet know what to do with.

From what I can see, support for producing Schema:EditConflict was added by personal request in 2014 and I don't think it was ever consumed. Data has not been sanitized, so there's no historical record to preserve. Data collected is redundant with TwoColConflictConflict, which is actively used.

I recommend dropping the event and all data.

If there is somehow a historical record of this table going back to 2014, please preserve, that would be valuable.

I'd like to see some discussion about the $wgPingback defaults. According to our documentation, the pingback checkbox is opt-out during installation. But this is a rather invasive setting, as far as I know it's the only thing in MediaWiki to "call home", and it reveals IP address, operating system, PHP and MediaWiki version. The data could be abused in many ways including as part of an attack. I would personally like to see this become opt-in, or at least see that there's already some kind of consensus that we—"we" being problematic here because that group likely doesn't include the new sysadmins sending the pingback—are okay with the current behavior.

Ottomata updated the task description. (Show Details)

After updating the audit spreadsheet, I removed more of the schemas we know what to do with from this task description.

SchemaMigrate or Decom?Owners?codesearch results?
UserFeedbackSSethi (WMF)yes

AIUI a gadget produced UserFeedback events and that gadget was undeployed (per T248892#6547896 and T248892#6557192). The Global Search tool yields no results for UserFeedback in the Gadget, Gadget_talk, Gadget_definition, and Gadget_definition_talk namespaces.

@srishakatux, @bd808: Do you know if the gadget is deployed anywhere else? If not, I'll submit a patch to remove the UserFeedback EventLoggingSchemas entry.

SchemaMigrate or Decom?Owners?codesearch results?
UserFeedbackSSethi (WMF)yes

AIUI a gadget produced UserFeedback events and that gadget was undeployed (per T248892#6547896 and T248892#6557192). The Global Search tool yields no results for UserFeedback in the Gadget, Gadget_talk, Gadget_definition, and Gadget_definition_talk namespaces.

@srishakatux, @bd808: Do you know if the gadget is deployed anywhere else? If not, I'll submit a patch to remove the UserFeedback EventLoggingSchemas entry.

It is not anywhere else, so +1 to removing. Thanks for the ping.

Change 769742 had a related patch set uploaded (by Phuedx; author: Phuedx):

[mediawiki/extensions/WikimediaEvents@master] Remove UserFeedback EventLoggingSchemas entry

https://gerrit.wikimedia.org/r/769742

Change 769742 merged by jenkins-bot:

[mediawiki/extensions/WikimediaEvents@master] Remove UserFeedback EventLoggingSchemas entry

https://gerrit.wikimedia.org/r/769742

phuedx updated the task description. (Show Details)

@Ottomata
The AdvancedSearchRequest data stream can be decommissioned. Sorry for the lag, this somehow slipped through.

Aklapper subscribed.

@Ottomata: Per emails from Sep18 and Oct20 and https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup , I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!). Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task. Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - it would be welcome. Thanks for your understanding!

Ottomata claimed this task.

There is only one remaining schema to migrate (T323828), so we have completed this task! We have 'determined' what to do with all schemas. Resolving!

SO MUCH THANKS TO @phuedx for hammering on the long tail of tasks.