JAllemandou added a comment.
Some more info on this aspect: I have done a quick analysis over September
queries today and found that my assumption that long queries were made by users
from UI is wrong.
First, total numbers of request and sum of query-time split by queries taking
more
Gehel closed this task as "Resolved".
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Zbyszko, Gehel
Cc: CBogen, JAllemandou, Aklapper, Gehel, Alter-paule, Beast1978, Un1tY,
Akuckartz, Hook696,
gerritbot added a comment.
Change 628755 **abandoned** by ZPapierski:
[wikidata/query/rdf@master] Add referer info to query event
Reason:
Not needed
https://gerrit.wikimedia.org/r/628755
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
JAllemandou added a comment.
I continued my analysis today looking at top-100 parsed user-agents from both
queries-with-referer subset, and queries-without-referer subset, over the month
of September.
See https://phabricator.wikimedia.org/P12933
- The queries-with-referer have a
JAllemandou added a comment.
Heya - I'm sorry I completely missed the ping :S
Quick analysis:
spark.sql("SELECT (http.request_headers['referer'] IS NOT NULL) as
defined_referer, count(1) as c from event.wdqs_external_sparql_query where year
= 2020 and month = 9 group by
CBogen added subscribers: JAllemandou, CBogen.
CBogen added a comment.
Hi @JAllemandou - any thoughts on Zbyszko's question above?
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Zbyszko,
Zbyszko added a comment.
It turns out that request headers already provide referrer (where available)
in http.request-headers map. Is it required to provide it elsewhere to fulfill
the need of analysts?
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
gerritbot added a comment.
Change 628757 **abandoned** by ZPapierski:
[schemas/event/secondary@master] Referer in query event
Reason:
There is already a request headers field in the event.
https://gerrit.wikimedia.org/r/628757
TASK DETAIL
gerritbot added a comment.
Change 628757 had a related patch set uploaded (by ZPapierski; owner:
ZPapierski):
[schemas/event/secondary@master] Referer in query event
https://gerrit.wikimedia.org/r/628757
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
gerritbot added a comment.
Change 628755 had a related patch set uploaded (by ZPapierski; owner:
ZPapierski):
[wikidata/query/rdf@master] Add referer info to query event
https://gerrit.wikimedia.org/r/628755
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
gerritbot added a project: Patch-For-Review.
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Zbyszko, gerritbot
Cc: Aklapper, Gehel, Alter-paule, Beast1978, CBogen, Un1tY, Akuckartz, Hook696,
Zbyszko claimed this task.
TASK DETAIL
https://phabricator.wikimedia.org/T261841
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Zbyszko
Cc: Aklapper, Gehel, CBogen, Akuckartz, darthmon_wmde, Nandana, Namenlos314,
Lahi, Gq86, Lucas_Werkmeister_WMDE,
Gehel set the point value for this task to "3".
Gehel moved this task from Incoming to Ready for Development on the
Discovery-Search (Current work) board.
Gehel added a comment.
HTTP referer should be enough (if not perfect). EventGate might already have
a place to log such information.
Gehel moved this task from Scaling to Current work on the
Wikidata-Query-Service board.
Gehel added a project: Discovery-Search (Current work).
TASK DETAIL
https://phabricator.wikimedia.org/T261841
WORKBOARD
https://phabricator.wikimedia.org/project/board/891/
EMAIL PREFERENCES
Gehel created this task.
Gehel added a project: Wikidata-Query-Service.
Restricted Application added a subscriber: Aklapper.
Restricted Application added a project: Wikidata.
TASK DESCRIPTION
As an analyst, I want to know where a query is coming from to better
understand the behaviour of our
15 matches
Mail list logo