Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're just now getting to grips with statsd+graphite, and we (think we) want to look at graphs sliced differently. For example, say we have a website foo that is multi-tenanted to 3 customers and served on 4 servers:

  1. aggregate (all servers, all tenants) across our whole service - so publish foo.logins.attempts:3|c
  2. aggregate by tenant (all servers) across our service - so publish|c
  3. individual servers across our service - so publish|c

What are the implications of

  1. publishing the stats 3 times (actually, one statsd call, with one stat per line), once each with each different prefix, so it's easier to find in statsd and graphite, and manipulate
  2. publishing the stat once (#3 above) and then using graphite to mix and match to produce the views that we want


share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.