As was done in V1, we want to log incoming queries and the status codes, and some auxiliary info like user-agent. This is really useful info for analyzing WDQS traffic.
This is done by configuring an EventStream with a given schema, and then HTTP POSTing events there to an eventgate URI. For reference, here's how it's done in V1.
The stream setup is being tracked in T429380. This ticket is tracking the work to set up the proxy to push events to the stream.
| 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 | lerickson | T429407 wdqs-proxy: post events to event streams |
lerickson updated https://gitlab.wikimedia.org/repos/wikidata-platform/wdqs/wdqs-proxy/-/merge_requests/45
Draft: Send events in the proxy
lerickson merged https://gitlab.wikimedia.org/repos/wikidata-platform/wdqs/wdqs-proxy/-/merge_requests/45
Send events to EventGate from the proxy.
Change #1311547 had a related patch set uploaded (by Lerickson; author: Lerickson):
[operations/deployment-charts@master] Add main/scholarly and internal/external specific configs for EventGate streams.
Change #1311547 merged by jenkins-bot:
[operations/deployment-charts@master] Add main/scholarly and internal/external specific configs for EventGate streams.