Last modified: 2014-10-20 14:34:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74138, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72138 - Story: WikimetricsUser monitors health of Wikimetrics in graphite
Story: WikimetricsUser monitors health of Wikimetrics in graphite
Status: NEW
Product: Analytics
Classification: Unclassified
Wikimetrics (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Nobody - You can work on this!
u=WikimetricsUser c=Wikimetrics p=9999
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-16 15:37 UTC by Kevin Leduc
Modified: 2014-10-20 14:34 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kevin Leduc 2014-10-16 15:37:04 UTC

    
Comment 1 Kevin Leduc 2014-10-16 15:40:22 UTC
use graphite to monitor health of the system.
Comment 2 Kevin Leduc 2014-10-16 15:40:47 UTC
Collaborative tasking:
http://etherpad.wikimedia.org/p/analytics-72138
Comment 3 christian 2014-10-20 13:31:30 UTC
For most services, WMF mostly uses Icinga to monitor them.

To me, it seems Icinga would also be a good fit for Wikimetrics too, as
wikimetrics has many parts that are “either working or not”, and does
up to my knowledge not so much depend on performance counters going up
and down.

How comes we want to use graphite?
Comment 4 Dan Andreescu 2014-10-20 13:33:24 UTC
The reason for graphite in the title of the bug is because of the new monitoring that's been made available in labs.  We assumed it was easy to add more monitoring using graphite, but we haven't looked into it.
Comment 5 christian 2014-10-20 14:34:09 UTC
So “graphite” is just a placeholder for $SOME_MONITORING_SERVICE?

Then just to have it written down ... in labs it seems we're getting (or
already having?) Shinken, which can consume Icingia config files IIRC.

So whoever ends up doing the Spike, might want to have look there too.

(YuviPanda would know more about Shinken.)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links