Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | KCVelaga_WMF | T350483 Track usage of MinT in the Translate extension | |||
| In Progress | Wangombe | T364460 Implement the instrumentation to track usage of MinT in the Translate extension |
Event Timeline
Change #1062367 had a related patch set uploaded (by Wangombe; author: Wangombe):
[mediawiki/extensions/TranslationNotifications@master] NotificationMessageBuilder: add `action_source` query param
Change #1046661 had a related patch set uploaded (by Wangombe; author: Wangombe):
[mediawiki/extensions/Translate@master] MinT: Add event logging to Translate
Change #1062367 merged by jenkins-bot:
[mediawiki/extensions/TranslationNotifications@master] NotificationMessageBuilder: add `action_source` query param
Change #1046661 merged by jenkins-bot:
[mediawiki/extensions/Translate@master] MVP: Add event logging to Special:Translate
T369687 has been resolved. Following this comment, we should now be able to proceed with implementing a number of other events that would eventually lead to a holistic picture when tracking usage of MinT in the Translate extension.
As a caveat, it was pointed out that a number of events and the related work items around them may not directly point at MinT instrumentation, though related. I think this is fine as long as it serves the end goal. There's a new configuration parameter, TranslateEnableEventLogging, that is disabled by default on wikis that have the Translate Extension installed. I expect another configuration parameter that is specific to MinT in upcoming patches.
T369687 has been resolved. Following this comment, we should now be able to proceed with implementing a number of other events that would eventually lead to a holistic picture when tracking usage of MinT in the Translate extension.
Yes, I have added a couple of columns to the schema (E & F) with information about what needs to changed from action_context to the schema fragment fields.
As a caveat, it was pointed out that a number of events and the related work items around them may not directly point at MinT instrumentation, though related. I think this is fine as long as it serves the end goal.
Yes, I think at this point the schema is more for the Translate extension, rather than specifically MinT only, as some of other events will have to be tracked for us to get a better understanding of the user interactions.
- schemaID = /analytics/product_metrics/web/translation/1.0.0
- streamName = mediawiki.product_metrics.translate_extension
A quick note (after I heard back from the Metrics Platform team), all events should have the translation object. If an event is not using any of the translation fields, it can be an empty object {}. This will ensure that those events pass EventGate validation.