Change Details

Let's find an example instrumentation to produce through the new Event Platform components this quarter. This can be something ported over from EventLogging, or it can be a new instrumentation event stream altogether. Nuria suggested perhaps a new MediaViewer views event? This should use all of the new analytics focused Event Platform client side componenets: [] New schema in schemas/event/secondary repository [] eventgate-analytics-external set up (otto) [] new eventLogging.client RL module produces event (Jason) [] Both eventgate-analytics-external and eventLogging.client use new EventStreamConfig extension (otto & Jason) This is a KR for Q3 2019-2020.

Let's find an example instrumentation to produce through the new Event Platform components this quarter. This can be something ported over from EventLogging, or it can be a new instrumentation event stream altogether. Nuria suggested perhaps a new MediaViewer views event? This should use all of the new analytics focused Event Platform client side componenets: [] New schema in schemas/event/secondary repository [x] eventgate-analytics-external set up (otto) [] new eventLogging.client RL module produces event (Jason) [x] Both eventgate-analytics-external and eventLogging.client use new EventStreamConfig extension (otto & Jason) This is a KR for Q3 2019-2020.

Let's find an example instrumentation to produce through the new Event Platform components this quarter. This can be something ported over from EventLogging, or it can be a new instrumentation event stream altogether. Nuria suggested perhaps a new MediaViewer views event? This should use all of the new analytics focused Event Platform client side componenets: [] New schema in schemas/event/secondary repository [x] eventgate-analytics-external set up (otto) [] new eventLogging.client RL module produces event (Jason) [x] Both eventgate-analytics-external and eventLogging.client use new EventStreamConfig extension (otto & Jason) This is a KR for Q3 2019-2020.