See T405949. In order to get more accurate query timing info without abusing the meta.dt field (which EventGate fills), we should create and use our own top-level dt field.
We should also fill this field in wdqs-proxy.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | gmodena | T431253 [DE2.4.2] WDQS v2 Scaling | |||
| Resolved | lerickson | T421200 wdqs-proxy: event platform integration for query logs | |||
| Resolved | trueg | T431480 Events: add top-level `dt` field to the event schema, and fill it. |
Event Timeline
Comment Actions
trueg opened https://gitlab.wikimedia.org/repos/data-engineering/schemas-event-secondary/-/merge_requests/130
development/sparql/query: added query_dt field
Comment Actions
trueg opened https://gitlab.wikimedia.org/repos/wikidata-platform/wdqs/wdqs-proxy/-/merge_requests/50
Write query timestamp to query events
Comment Actions
trueg merged https://gitlab.wikimedia.org/repos/data-engineering/schemas-event-secondary/-/merge_requests/130
development/sparql/query: added query_dt field
Comment Actions
trueg merged https://gitlab.wikimedia.org/repos/wikidata-platform/wdqs/wdqs-proxy/-/merge_requests/50
Write query timestamp to query events