[Wikidata-bugs] [Maniphest] [Commented On] T178533: Find out why nginx log in logstash has no 429s

2017-11-06 Thread gerritbot
gerritbot added a comment. Change 388696 merged by Gehel: [operations/puppet@production] Report 429s to logstash too https://gerrit.wikimedia.org/r/388696TASK DETAILhttps://phabricator.wikimedia.org/T178533EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T178533: Find out why nginx log in logstash has no 429s

2017-11-03 Thread gerritbot
gerritbot added a comment. Change 388696 had a related patch set uploaded (by Smalyshev; owner: Smalyshev): [operations/puppet@production] Report 429s to logstash too https://gerrit.wikimedia.org/r/388696TASK DETAILhttps://phabricator.wikimedia.org/T178533EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T178533: Find out why nginx log in logstash has no 429s

2017-11-03 Thread Smalyshev
Smalyshev added a comment. Looks like I found the reason - we use proxy_intercept_errors which sends 429 to separate location block, and that block does not have logstash access log configured.TASK DETAILhttps://phabricator.wikimedia.org/T178533EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T178533: Find out why nginx log in logstash has no 429s

2017-11-03 Thread Smalyshev
Smalyshev added a comment. From my tests on wdqs-test, looks like 429 is reported to /var/log/nginx/access.log but not into logstash or access log that is inside SPARQL location clause. Not sure why is that.TASK DETAILhttps://phabricator.wikimedia.org/T178533EMAIL