On Jul 30, 2012, at 2:33 PM, Terry Chay wrote:
Thanks for starting this thread. Diederik and I already shut down several undocumented data collection jobs that nobody owned months ago (one of the problems of CT is that anything/anyone can start dumping data into the log by calling the API calls, without identifying itself).
These are features currently logging events into emery:/var/aft/log/clicktracking.log
- ext.articleFeedback (AFT4)
- currently collecting data from enwiki, eswiki, ptwiki, zhwiki, testwiki; enwiki will be entirely disabled with the completion of the AFTv5 ramp-up, I don't know why we are still collecting data from other wikis unless this was commissioned by Global Dev. I recommend we discontinue AFTv4 logging on all wikis.
Yes, let's let this one die and see if anyone complains. BTW, orthogonal to this discussion we should see is the possibility of turning off AFTv4 entirely. The reason is AFTv5 to 100% will be blocked on performance considerations, but I got the impression that English doesn't even care for AFTv4 anymore.
Yes, my understanding is that we are ready to disable AFT4 entirely, at least from a WMF product team standpoint.
I announced in two successive blog posts that we would retire it in September, when we deploy AFT5 to 100%, so people who read our blog may already be aware of this planned change.
But we may want to do one final community outreach before turning it off completely.
Does anyone have recommendations on how we might do this final communication? I suspect the folks who would care the most may be researchers, rather than community members ...
- ext.articleFeedbackv5 (AFT5)
- entirely disabled on enwiki, but events keep trickling in from users running stale code. It can be safely discontinued unless there's a need of resuming data collection for FeedbackPage usage or CTAs after the completion of the ramp-up (Fabrice's call).
Whee! Let's plan that if Fabrice needs something new, they will be handled by the E3_experiments extension going forward.
Sounds good to me.
When do we expect to have access to the E3 clicktracking function? We may want to collect some data on the feedback page after we deploy successfully to 100%, which could be anywhere from mid-September to late October, depending on how our scaleability analysis goes in a couple weeks.
- ext.MoodBar
- collecting email notification click-through data from enwiki, will be disabled at the latest by August 15.
Ori can decide if this needs to be moved.
- E3 experiments (PEF, Community Portal)
- collecting clickthrough and edit save completion data on enwiki, will be moved to vanadium as soon as it's ready to collect data.
I am not aware of any other features/gadgets currently using the ClickTracking extension.
Dario
On Jul 27, 2012, at 2:42 PM, Terry Chay wrote:
The idea is to fold all of editor engagement data collection and analysis into the tool/services that Ori is building out on vanadium. If we can shut down clicktracking and udp2log, then we can not only start collecting this data again soon, but also increase what we collect, and do analytics faster.
In the short term, since this is editor data (logged in usage), this can all be handled on vanadium. In the longer term, these will be queries on Kraken.
BTW, I don't know when it would be "removed" but at the minimum, if other things are delayed, clicktracking might get "broken" for old data streams unless we specifically support them.
However, we will want to start collecting clicktracking data again soon, so my hope is that we can have a solution for that in coming weeks.
_______________________________________________
ee mailing list
ee@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ee
ee mailing list
ee@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ee
ee mailing list
ee@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ee