Sun, May 31
I've moved everything off of both notebook servers. Thanks, @elukey!
Thu, May 28
Fri, May 22
@SNowick_WMF between us giving Andrew some good feedback and Newpyter getting deprioritized for now, I think this is done. Feel free to reopen if you disagree 😊
Wed, May 20
I'm now not seeing any events geolocating to Ashburn, Virginia, United States, where CircleCI's servers are located.
Since the patch was merged, I'm (1) seeing many pageviews with multiple events and (2) not seeing pageviews with long page open times but short page visible times, since those are now split up into separate pageviews. So this looks good!
Mon, May 18
The Legal team looked into this and said they do not see any legal impediment to either choice, as long as we are clear and consistent about it.
I looked at this again, and it was actually very easy (redirecting one page and removing unnecessary content from another), so I just did it 🙂
Thu, May 14
Wed, May 13
Mon, May 11
@mpopov should we not use a repo like analytics/wmf-product/jobs? We'll want repos for other things as well; I'll want analytics/wmf-product/wmfdata-python, for example 🙂
Wed, May 6
We haven't seen any page visible times longer than an hour in the past few weeks, so it seems like this has been fixed!
Yesterday, @SBisson and I decided to improve the way we split up sessions and pageviews (T251909). At first glance, those changes will not solve this issue, but since they will impact so much that's potentially related, it's worth waiting until it's done and then checking again.
Tue, May 5
New Readers has no particular need for this; moving to the general research ideas project.
I've just updated the task description with the most recent information. Here are all the events from the three most recent installs with incorrect session interrupts (one each from @SGautam_WMF, @SBisson, and @eamedina). I've bolded the incorrectly regenerated session ID.
Mon, May 4
Apr 27 2020
Apr 20 2020
We had the quarterly insights meeting a while ago, so this seems to be done!
@SBisson, the purpose of the "Analytics" column is to track the work meant for me. Obviously, that wasn't clear, so I'm renaming the column to "analyst" and moving this task out 😊
There's no specific request for Product Analytics here, so moving to our tracking column.
Apr 19 2020
We will triage this request at our team meeting tomorrow (Mon, 19 Apr).
Apr 16 2020
We haven't seen any Spark problems in a while, so moving this to the backlog while we wait to see if this is actually needed.
@hueitan, thanks for investigating! I discussed this with @AMuigai and @SBisson on Tuesday in the weekly sync, and since it's possible that the old code was runnigng even last week, we decided that I would look at this at the start of next week.
These are now in Superset!
We are now using Superset, which means that auto-publication comes for free. T226170 and T233022 aren't possible using the current Druid datasets, but T239903 should make it possible to add them using Presto. The Superset-Presto integration is still a bit rough, but I'm confident it will all be worked out by the time we're ready to add those extra metrics.
We are now using Superset, which means that interactive visualizations come for free. T226170 and T233022 aren't possible using the current Druid datasets, but T239903 should make it possible to add them using Presto. The Superset-Presto integration is still a bit rough, but I'm confident it will all be worked out by the time we're ready to add those extra metrics.
@Pginer-WMF, when might section translation be released? I imagine we want to do get this done around the same time.
@Rmaung, thank you for filing this! We'll prioritize this at our upcoming triage meeting on Monday, 20 April.
It looks like Product-Analytics is tagged just for information. If this is a request for us to do something, please move it back to the "triage" column on our workboard.
Apr 15 2020
@Mayakp.wiki and I discussed this analysis idea in detail yesterday, and unfortunately I don't think it's actually feasible, because there isn't a good way to determine which comments actually get replies.
Looks this is done.
Apr 13 2020
@AMuigai, @Rileych FYI, this is primarily within the engineers' sphere since the issue is almost certainly with the instrumentation code. Of course, I'm still here to help with brainstorming or checking hypothesis against the existing data!
Apr 10 2020
We don't have any specific plans to work on this, although it would still be useful to research.
The revision_tags_change table has been around long enough now that we're unlikely to need older data in the same format.