Page MenuHomePhabricator

Metrics Platform Schema: Define & Model Event Level Fields
Closed, ResolvedPublic

Description

Goal: Identify what an event is and field level events we should be capturing.

Impact:

  • Consistently generate events across instrumentations so that they are easy to find, identify, and consume

Success Criteria:

  • Clearly define what an event is and when to generate it (ex: event = event + event_name)
  • Determine fields required to uniquely identify events, pull common events
  • Model the event level fields and test

Related Objects

Event Timeline

DAbad renamed this task from Define Event Level Fields to Metrics Platform Schema: Define Event Level Fields.May 5 2021, 4:34 PM
DAbad triaged this task as High priority.
DAbad updated the task description. (Show Details)
DAbad renamed this task from Metrics Platform Schema: Define Event Level Fields to Metrics Platform Schema: Define & Model Event Level Fields.May 13 2021, 4:05 PM
DAbad updated the task description. (Show Details)
Aklapper added a subscriber: DAbad.

Removing inactive task assignee. (Please do so as part of offboarding - thanks.)

Oh, or perhaps the subtasks should be done first?

I've been bold and removed two subtasks that I don't think are related to this epic. T267217: MediaWiki Session ID should have per-subdomain and cross-subdomain variants is a feature request for someone – I don't think there's formal ownership of session IDs but Data Products does seem like a good fit so I've tagged it as such. T267602: Client-side error logging should use Elastic Common Schema (ECS) fields when possible isn't related to Metrics Platform work.

I can see a future in which we use client-side error count as a guardrail but that's an epic in and of itself since we have to consider filtering errors caused by user scripts, gadgets, and banners, which is non-trivial (see T361680: CentralNotice should catch banner errors and log them to its own channel).

Ottomata claimed this task.

Being bold and closing this old task. The remaining subtask are event platform level and are in progress.