In T267648: Adopt conventions for server receive and client/event timestamps in non analytics event schemas, we want to use dt as the event time for all event schemas.
Going foward, all new schemas do this. We can and should easily make the error event schema use this too.
This will be used by T326536: Streaming services errors should be routed to an error event topic..
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| error/2.0.0 - add dt field | schemas/event/primary | master | +111 -5 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T259734 BUOD-KR1-Q4+: Certify that analytics schema and instruments have been upgraded to use the MEP system (clearing the legacy system for sunsetting) | |||
| Declined | Ottomata | T259157 BUOD-KR1-Q3: Require that all new schema/instruments are created with the MEP system | |||
| Declined | None | T259704 BUOD-KR1-Q2: Upgrade MEP clients to full release status | |||
| Resolved | Ottomata | T240462 Review and evolve client environment around EventLogging | |||
| Resolved | • jlinehan | T240460 Clients need to generate an ISO 8601 formatted timestamp | |||
| Open | None | T281999 Metrics Platform Schema: Define & Model Event Level Fields | |||
| Open | None | T267648 Adopt conventions for server receive and client/event timestamps in non analytics event schemas | |||
| Resolved | Ottomata | T330918 Add event dt field to error event schema |
Change 893518 had a related patch set uploaded (by Ottomata; author: Ottomata):
[schemas/event/primary@master] error/2.0.0 - add dt field
Change 893518 merged by jenkins-bot:
[schemas/event/primary@master] error/2.0.0 - add dt field