Fri, Jun 21
Strangely, looking at revision/create raw events, their meta: property is the same, there are no structural differences between that and the page-links-change events.
Thu, Jun 20
for the record: decided to drop old table, event.mediawiki_page_restrictions_change_T226051.
Having a bit of an issue setting up the MobileFrontEnd repo and submitting a patch, so a little more delay on that. Everything else looks to be done. This looked machine generated so I didn't try to change anything: https://gerrit.wikimedia.org/g/operations/mediawiki-config/+/68c4ebcf6a42f0c04d8a5e8b068071a840faa54c/docroot/wikipedia.org/speed-tests/Banksy.enwiki.872156204/startup.js#48
yes, this is the output when I try to git commit after fixing the things I mentioned. I decided not to go forward and try to install parallel-lint manually because the composer.json file in the repository seems to have it as a dependency:
Wed, Jun 19
Mon, Jun 17
just chown-ed the glent.db files to analytics-search, Andrew will remove the content from the home directories.
In @Volker_E's review of the Matomo-generated client code, a mistake was made that caused the client to ping the admin interface instead of where it should be going - the event tracking: https://gerrit.wikimedia.org/r/#/c/oojs/ui/+/516591/1..6/demos/index.html
The only relevant work I can think of is the comparison of VE and Wikitext editing we did with these queries: https://github.com/wikimedia/analytics-limn-edit-data/tree/master/edit
Fri, Jun 14
Thu, Jun 13
Wed, Jun 12
Thu, Jun 6
Wed, Jun 5
+1, either hops is doing some incredible organic marketing or their ideas and libraries are good and people are using it. I also like their plan to use https://github.com/uber/petastorm, and I think we should consider incorporating parts of their stack even if we don't stand up a Hops cluster.
Good point, I only looked for "using" statements. I'll add subtasks and merge patches for all those uses in the next couple of weeks.
May 23 2019
For what it's worth one of our projects uses requirejs and karma (analytics-dashiki), so if anyone wants to try that out I can show them how to make it work.
May 22 2019
Oh yeah, we missed that one because it’s in the reportupdater-queries repository already. I’ve added it to my comment above with the others.
May 20 2019
@Ottomata I think what you and Luca are proposing would work well to address this task. But we could spend some time brainbouncing a very user-friendly way for people to see these logs. It would solve MEP's requirement to make it easier to debug instrumentation in beta and there's no reason we couldn't use it for EventLogging until everything migrates over to MEP.
Superset will probably timeout for most Hive queries. In Superset we want to query faster datasources like Presto (coming up) and Druid. It's just not an async job execution tool like Quarry.
May 16 2019
considerations: privacy so that events can't be read by everyone. Andrew should weigh in as this solution could be shared by MEP
There are basically three reports that need to be moved (the only remaining reports that crunch EventLogging data):
@Yurik I think in general graphoid is going to find a sponsor, but I'm not 100% clear on who exactly that is. One of the 3 main strategies for the next 3-5 years is "rich media" so this obviously fits in. The code that @Xiaoyanghaitao is working on to add Vega support to the Graph extension seems useful in any case. The more foundational platform work should include a better way for graphoid to interact with mediawiki (better than page props). And other work that's been described on this and related tasks. I don't think it makes sense to do it in context of GSoC though, the Graph extension work fits much better there. I'm a little late to the party, and I see you're reviewing the code, but I can take a look if either you or @Xiaoyanghaitao would find that useful.
To clear up what Joseph said, we're never going to have more than 90 days of geolocated edits for privacy reasons. We do have two aggregated datasets that go back more than a year:
Sentry extension change ready to review ^
all known blockers are subtasks of this tasks and they have all been completed. I guess the next step is to let it bake a little and remove the actual schema modules.
May 15 2019
May 14 2019
UPDATE: if you saw the message below you can just disregard it, I'll do it a simpler way and send a patch soon. We're fine using logEvent and you can move to mw.track later if you like. Apologies for the noise.