[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2017-07-10 Thread Smalyshev
Smalyshev added a comment. @Izno yes, pasted in a wrong window :)TASK DETAILhttps://phabricator.wikimedia.org/T119915EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Gehel, SmalyshevCc: Izno, Dzahn, gerritbot, Gehel, Ricordisamoa, hoo, Addshore, Aklapper,

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2017-07-10 Thread Izno
Izno added a comment. In T119915#3421698, @Smalyshev wrote: Implemented as geof:globe, geof:latitude & geof:longitude @Smalyshev Did you mean to close and out this resolution on the globe task you closed today?TASK DETAILhttps://phabricator.wikimedia.org/T119915EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2017-07-10 Thread Gehel
Gehel added a comment. The UNKNOWN disappeared now that we are active/active. Previously, when no traffic was sent to codfw, we had no meaningful data about response time. This can be closed again.TASK DETAILhttps://phabricator.wikimedia.org/T119915EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2017-07-10 Thread Smalyshev
Smalyshev added a comment. Implemented as geof:globe, geof:latitude & geof:longitudeTASK DETAILhttps://phabricator.wikimedia.org/T119915EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Gehel, SmalyshevCc: Dzahn, gerritbot, Gehel, Ricordisamoa, hoo, Addshore,

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2017-04-18 Thread Dzahn
Dzahn added a comment. The Icinga/graphite check "Response time for WDQS" is in status "UNKNOWN" because there are "No valid datapoints found". https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2=einsteinium=Response+time+of+WDQS This is a common problem with Icinga/Graphite checks

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2016-05-04 Thread gerritbot
gerritbot added a comment. Change 286992 merged by Gehel: Add response time checks to WDQS https://gerrit.wikimedia.org/r/286992 TASK DETAIL https://phabricator.wikimedia.org/T119915 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To:

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2016-05-04 Thread gerritbot
gerritbot added a comment. Change 286992 had a related patch set uploaded (by Gehel): Add response time checks to WDQS https://gerrit.wikimedia.org/r/286992 TASK DETAIL https://phabricator.wikimedia.org/T119915 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2016-05-04 Thread Addshore
Addshore added a comment. Just looking at the other things I am recording right now but it may infact make sense to put a monitor on the Done Rate or the Queries Per Second. A Done Rate of 0 or a QPS of 0 for longer than the normal query timeout should shout at us, as it means no

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2016-05-04 Thread Smalyshev
Smalyshev added a comment. I think we need to at least put monitor on whatever "varnish latency" counts and alert say if it's over 30 s. TASK DETAIL https://phabricator.wikimedia.org/T119915 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To:

[Wikidata-bugs] [Maniphest] [Commented On] T119915: Create response time monitoring for WDQS endpoint

2016-02-03 Thread Addshore
Addshore added a comment. It should be noted we just had an partial outage for 6/7 hours without us noticed ;) wdqs1002 seemed to totally die but nothing pinged anyone. wdqs1001 seemed to stop updating (resulting in a warning in icinga) but again it doesn't seem to have pinged anyone.