We currently store the logging time twice: once in the MsgId (soon EventId) and once injected by the SDK (and they don't even match!).
We could just not inject the log_time, and instead derive a log_time column on the server using the timestamp in the EventId; especially since we probably want an auto-derived ingestion_time anyway.
The timestamp in EventId is not going away: it is what defines our global ordering!
We currently store the logging time twice: once in the
MsgId(soonEventId) and once injected by the SDK (and they don't even match!).We could just not inject the
log_time, and instead derive alog_timecolumn on the server using the timestamp in theEventId; especially since we probably want an auto-derivedingestion_timeanyway.The timestamp in
EventIdis not going away: it is what defines our global ordering!