As an analyst, I want more context with the queries logged to EventGate so that I can better understand the queries and their impact.
We've talked in T248308#6062499 about adding CPU load or the current number of running queries to our query logging. This seems fairly easy to do, so we should probably "just do it (tm)" and check if we get any value out of it.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dcausse | T221938 [Epic] Scaling strategy for Wikidata Query Service | |||
| Resolved | Gehel | T257045 [Epic] Better understanding of WDQS users and use cases | |||
| Resolved | • Zbyszko | T261937 Add CPU load and query concurrency as context to event logging from WDQS |
Will make it a lot easier to analyze than to have to build the 'in-flight' view of queries!
Change 628139 had a related patch set uploaded (by ZPapierski; owner: ZPapierski):
[wikidata/query/rdf@master] Add CPU load an query concurrency to query events
Change 628327 had a related patch set uploaded (by ZPapierski; owner: ZPapierski):
[schemas/event/secondary@master] Added system_runtime_metrics into query event
Change 628327 merged by ZPapierski:
[schemas/event/secondary@master] Added system_runtime_metrics into query event
Change 628139 merged by jenkins-bot:
[wikidata/query/rdf@master] Add CPU load an query concurrency to query events