Fozzie travis-ci

Ruby gem for registering statistics to a Statsd server in various ways.


  • A Statsd server
  • Ruby 1.9

Basic Usage

Send through statistics depending on the type you want to provide:

Increment counter

Stats.increment 'wat' # increments the value in a Statsd bucket called 'some.prefix.wat' -
                      # the exact bucket name depends on the bucket name prefix (see below)

Decrement counter

Stats.decrement 'wat'

Decrement counter - provide a value as integer

Stats.count 'wat', 5

Basic timing - provide a value in milliseconds

Stats.timing 'wat', 500

Timings - provide a block to time against (inline and do syntax supported)

Stats.time 'wat' { sleep 5 }

Stats.time_to_do 'wat' do
  sleep 5

Stats.time_for 'wat' { sleep 5 }

Gauges - register arbitrary values

Stats.gauge 'wat', 99

Events - register different events








With a custom app: ``` ruby Stats.deployed 'watapp'

Stats.deploy ```

With a custom app: ruby Stats.deploy 'watapp'


Stats.event 'pull'

With a custom app:

Stats.event 'pull', 'watapp'

Boolean result - pass a value to be true or false, and increment on true

Stats.increment_on 'wat', duck.valid?


Each of the above methods accepts a sample rate as the last argument (before any applicable blocks), e.g:

Stats.increment 'wat', 10

Stats.decrement 'wat', 10

Stats.count 'wat', 5, 10


You can monitor methods with the following: ``` ruby class FooBar

_monitor def zar # my code here... end

_monitor("") def quux # something end

end `` This will register the processing time for this method, everytime it is called, under the Graphite bucketfoo_bar.zar`.

This will work on both Class and Instance methods.


You can send a bulk of metrics using the bulk method: ruby Stats.bulk do increment 'wat' decrement 'wot' gauge 'foo', rand time_to_do 'wat_timer' { sleep 4 } end

This will send all the given metrics in a single packet to the statistics server.


Fozzie supports the following namespaces as default

Stats.increment 'wat'
S.increment 'wat'
Statistics.increment 'wat'
Warehouse.increment 'wat'

You can customise this via the YAML configuration (see instructions below)


Fozzie is configured via a YAML or by setting a block against the Fozzie namespace.


Create a fozzie.yml within a config folder on the root of your app, which contains your settings for each env. Simple, verbose example below.

  appname: wat
  host: ''
  port: 8125
  namespaces: %w{Foo Bar Wat}
  prefix: %{foo bar car}
  appname: wat
  host: 'localhost'
  port: 8125
  namespaces: %w{Foo Bar Wat}
  appname: wat
  host: ''
  port: 8125
  namespaces: %w{Foo Bar Wat}

Configure block

Fozzie.configure do |config|
  config.appname = "wat"    = ""
  config.port    = 8125
  config.prefix  = []


You can inject or set the prefix value for your application.

Fozzie.configure do |config|
  config.prefix = ['foo', 'wat', 'bar']
Fozzie.configure do |config|
  config.prefix << 'dynamic-value'

Prefixes are cached on first use, therefore any changes to the Fozzie configure prefix after first metric is sent in your application will be ignored.


To time and register the controller actions within your Rack and Rails application, Fozzie provides some middleware.


require 'rack'
require 'fozzie/rack/middleware'

app = {
  use Fozzie::Rack::Middleware
  lambda { |env| [200, {'Content-Type' => 'text/plain'}, 'OK'] }


See Fozzie Rails.

Bucket name prefixes

Fozzie automatically constructs bucket name prefixes from app name, hostname, and environment. For example:

Stats.increment 'wat'

increments the bucket named text app-name.your-computer-name.development.wat

When working on your development machine. This allows multiple application instances, in different environments, to be distinguished easily and collated in Graphite quickly.

The app name can be configured via the YAML configuration.

Low level behaviour

The current implementation of Fozzie wraps the sending of the statistic in a timeout and rescue block, which prevent long host lookups (i.e. if your stats server disappears) and minimises impact on your code or application if something is erroring at a low level.

Fozzie will try to log these errors, but only if a logger has been applied (which by default it does not). Examples:

require 'logger'
Fozzie.logger =
require 'logger'
Fozzie.logger = 'log/fozzie.log'

This may change, depending on feedback and more production experience.


Currently supported and maintained by Marc Watts @ Lonely Planet Online.

Big thanks and Credits:

Comments and Feedback

Please contact me on anything... improvements will be needed and are welcomed greatly.