Done.

Change 743469 had a related patch set uploaded (by Jdlrobson; author: Jdlrobson):

[mediawiki/extensions/WikimediaEvents@master] Disable reading depth on special pages

https://gerrit.wikimedia.org/r/743469

This is happening on Special:CreateAccount where on-wiki code is disabled (though browser extensions of course aren't). And only happening there - if something changed $ I'd expect way more / worse breakage.

Tldr: user scripts/extensions might be removing $.cookie

...which does have the right dependency so I have no idea what's going on here.

I've updated the schema's documentation/talk page on metawiki.

Change 626116 merged by jenkins-bot:
[mediawiki/extensions/WikimediaEvents@master] ReadingDepth: Remove ReadingDepth instrument

In T229042#6445204, @Krinkle wrote:

The production payload for readingDepth.js is still being transferred and parsed on all page views. Can this be removed?

Change 626116 had a related patch set uploaded (by Phuedx; owner: Phuedx):
[mediawiki/extensions/WikimediaEvents@master] ReadingDepth: Remove ReadingDepth instrument

The production payload for readingDepth.js is still being transferred and parsed on all page views. Can this be removed?

Declining, ReadingDepth instrumentation is been turned off

Closing this since we decided to deactivate the readingdepth schema (T229042); we'll have to tackle something like this when sessionLength goes live.

Moving this off Reader's Webs board the original request of the team has been fulfilled.

This event is now deactivated, closing.

@Groceryheist with our very limited resources (more so this year than in years past) we really cannot afford to maintain streams this high volume that have no immediate use, and, even at low volume, it is my impression that nobody at the WMF is actually relying on this data.

Per the above, I've updated the documented sample, contact details, team, and project in the schema's documentation.

Discussed with @kzimmerman today and decided the best option forward would be to transfer ownership of the schema to the product analytics team (@mpopov, @jlinehan)

Change 531489 merged by Elukey:
[operations/puppet@production] profile::analytics::refinery::job::druid_load: absent readingdepth job

Sorry I lost track of this bug until today. I think it is really regrettable to turn off the instrumentation. The utility of the data is greatly lessened by gaps in the collection window.My understanding is that the instrument should only send two events for each page view. The sampling rate has been quite high at 10%, explaining the high number of events.

A slightly prettier Grafana graph 😉: https://grafana.wikimedia.org/d/000000018/eventlogging-schema?orgId=1&var-schema=ReadingDepth&from=1566302400000&to=1566388800000

@Groceryheist the data stream is been deactivated (this means that instrumentation is not sending data, but instrumentation is still present)

Change 531489 had a related patch set uploaded (by Nuria; owner: Nuria):
[operations/puppet@production] Removing loading of Reading_Depth into druid

Thanks Nuria!