Skip to content
This repository has been archived by the owner on Apr 21, 2020. It is now read-only.

Metrics

CodeBlock edited this page Apr 8, 2013 · 5 revisions

Keeping metrics is a great way to monitor Eval.so's health. It shows us painpoints that need work, as well has trending data, which makes it easier to predict when something will become overloaded.

Our metrics system has been implemented and looks like this:

  • Carbon persists our metrics data (whisper files).
  • Bucky relays metrics data to Graphite by receiving messages on the statsd protocol.
  • Graphiti acts as our dashboard to Graphite. (not yet implemented)
  • play-statsd relays stats from Frontend to Bucky.

In other words, Frontend -> Bucky -> Graphite -> Graphiti

Infrastructure-wise, every Frontend server will run Bucky alongside it. Graphiti and Carbon reside on another server (http://metrics.eval.so/).

Clone this wiki locally