Gehel added a comment.
@debt: as @Smalyshev said the right graph is all log messages.TASK DETAILhttps://phabricator.wikimedia.org/T172774EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev, GehelCc: debt, mpopov, chelsyx, Aklapper, PokestarFan, Smalyshev
Smalyshev added a comment.
@debt I think these are two separate graphs, the left is for throttling, the right is for all log messages.TASK DETAILhttps://phabricator.wikimedia.org/T172774EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: debt, mpopov,
debt added a comment.
Thanks for setting that up, @Gehel - I do have a question about the last 7 days of the chart, looking at who was throttled. Did we end up also throttling ourselves with the blazegraph work that @Smalyshev is working on?
F9343340: Screen Shot 2017-09-05 at 11.50.21 AM.pngTASK
Gehel added a comment.
A very minimal Wikidata Query Service Kibana dashboard now exists. There is a visualisation of throttling events over time (which includes all logs related to throttling, not just actual throttling).TASK DETAILhttps://phabricator.wikimedia.org/T172774EMAIL PREFERENCEShttps://
Gehel added a comment.
@debt now that we have logs sent to logstash, we should be able to create a dashboard for that. I need to learn how to do dashboards in Kibana, but I should learn that anyway...TASK DETAILhttps://phabricator.wikimedia.org/T172774EMAIL PREFERENCEShttps://phabricator.wikimedia.
Smalyshev added a comment.
I wonder now that we have logs parsed in logstash with user agents and statuses in separate fields could we have a nice graph showing how many requests were throttled and maybe distribution of user agents? Could add them to https://grafana.wikimedia.org/dashboard/db/wikid
Gehel added a comment.
16 hours after deployment, ~900 requests have been throttled (for a total of ~30k requests, so ~3% of requests are being throttled).
~650 of those requests are obviously by bots. We might want to contact the bots owner (where possible) to see if the restriction is affecting
