Ori, I think the Vector extension is creating those events.
On Fri, Jul 27, 2012 at 3:55 PM, Ori Livneh <ori.livneh(a)gmail.com> wrote:
Event IDs logged using ClickTracking extension in the
past 30 days:
http://dpaste.com/hold/776542/
Dario, I think your list accounts for all of them, except perhaps the
ext.vector.* and leftnav-vector-* event types. Do you know what those are?
On Friday, July 27, 2012 at 3:11 PM, Dario Taraborelli 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.
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).
ext.MoodBar
collecting email notification click-through data from enwiki, will be
disabled at
the latest by August 15.
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.
>
>
> On Jul 27, 2012, at 2:24 PM, Fabrice Florin <fflorin(a)wikimedia.org(mailtolto:
fflorin(a)wikimedia.org)> wrote:
> > 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(a)lists.wikimedia.org (mailto:ee@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/ee
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org (mailto:Analytics@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/analytics
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics