Page MenuHomePhabricator

CirrusSearch should send instances of Search backend error to graphite
Closed, ResolvedPublic

Description

Currently our visiblity into failure to contact the search cluster isn't great. We can do:

fluorine:/a/mw-log# grep 'Search backend error' /a/mw-log/hhvm.log | grep 'Operation timed out' | wc -l
15

But it would be infinitely better if we could begin tracking this in graphite as we will be able to reference the user impacting effects of our upgrade process and general cluster health.

Event Timeline

chasemp created this task.Aug 14 2015, 6:55 PM
chasemp raised the priority of this task from to Normal.
chasemp updated the task description. (Show Details)
chasemp added projects: Elasticsearch, Discovery.
chasemp added subscribers: EBernhardson, Krenair, dcausse and 2 others.

Change 232659 had a related patch set uploaded (by EBernhardson):
Report instances of backend errors to graphite

https://gerrit.wikimedia.org/r/232659

EBernhardson set Security to None.

Change 232659 merged by jenkins-bot:
Report instances of backend errors to graphite

https://gerrit.wikimedia.org/r/232659

Deskana closed this task as Resolved.Sep 9 2015, 2:36 AM
Deskana moved this task from Done to Resolved on the Discovery-Search (Current work) board.
Deskana added a subscriber: Deskana.