Review and evolve client environment around EventLogging
Open, LowPublic
Actions

Assigned To

Authored By

	jlinehan
	Dec 11 2019, 3:22 PM

Description

In the course of our discussions and code review for T238544: MEP Client MediaWiki JS (MVP) and T235189: Develop small client-side error logger for MediaWiki , we've identified a number of questions about architecture and the availability of certain methods in the client environment. These need to be resolved, possibly with patches but maybe through decisions we can make simply by discussing the matter more closely.

This task collects that work, which we would loosely hope to be completed before the end of FY 2019-20, although there is no firm triage right now.

Related Objects
Search...

Status	Assigned	Task
Open	None	T185233 Modern Event Platform
Open	Ottomata	T238230 Decommission EventLogging backend components by migrating to MEP
Open	jlinehan	T259734 BUOD-KR1-Q4+: Certify that analytics schema and instruments have been upgraded to use the MEP system (clearing the legacy system for sunsetting)
Open	jlinehan	T259157 BUOD-KR1-Q3: Require that all new schema/instruments are created with the MEP system
Open	jlinehan	T259704 BUOD-KR1-Q2: Upgrade MEP clients to full release status
Open	jlinehan	T240462 Review and evolve client environment around EventLogging
Open	jlinehan	T240454 Consider how to best architect transmission of events
Resolved	mpopov	T240452 Consider simplifying EventLogging dependency on mw.user's random ID generation
Resolved	jlinehan	T240461 Clients may need to generate a UUID for sending events.
Resolved	jlinehan	T240460 Clients need to generate an ISO 8601 formatted timestamp
Open	None	T267648 Adopt conventions for server receive and client/event timestamps in non analytics event schemas
Resolved	mpopov	T251281 Clients may need to set wiki/domain/webHost in event metadata