Seismograph

A helper library for writing metrics and events to (http://datadoghq.com)

Add this line to your application's Gemfile:

gem 'seismograph'

If not using bundler, be sure to require the gem:

require 'seismograph'

Configure your statsd server:

Seismograph.config do |config|
  config.app_name    = 'cabbagepult'  # optional
  config.env         = 'staging'      # optional, defaults to `RAILS_ENV` or `RACK_ENV`
  config.statsd_host = ENV.fetch('STATSD_HOST')
  config.statsd_port = ENV.fetch('STATSD_PORT')
end

After creating a sensor that designates a metric namespace, you can write values to it:

require 'seismograph'

def sensor
  @_sensor ||= Seismograph::Sensor.new('account')
end

def create
  users_to_create = [user1, user_2]

  sensor.count('signup', users_to_create.size) do
    # If an error is raised, the 'account.signup.failure' metric will be incremented instead
    User.create!(users_to_create)
  end
end

Counting is useful for tracking simple quantities or events. It accepts a numeric value (default is 1) and an optional block. In addition to counting, this method will also track success or failure (via incrementing) depending on whether an error is raised.

sensor.count('signup', 2)

sensor.count('signup') do
  User.create!(attributes)
end

Benchmarking is useful for tracking how long an operation takes. In addition to tracking the timing, this method will also track success or failure (via incrementing) depending on whether an error is raised.

def create
  sensor.benchmark('signup') do
    # Timing will be written for the account.signup metric
    User.create!(params)
  end
end

Timing is useful for tracking how long an operation takes, when that operation has already been run. For example, in the subscriber to an ActiveSupport::Instrumentation event. Expects the duration argument to be in ms (which the ActiveSupport event.duration already is).

class ActiveJobSubscriber < ActiveSupport::Subscriber

  attach_to :active_job

  def perform(event)
    job = event.payload[:job]
    tags = ["jobs:#{job.name}", "queue:#{job.queue_name}"]

    sensor.timing "perform", event.duration, sample_rate: 0.5, tags: tags
  end

  def sensor
    @sensor ||= Seismograph::Sensor.new("active_job")
  end

end

Simple incrementing and decrementing can be performed on a stat. Both methods accept a numeric value (default is 1).

sensor.increment('memberships')
sensor.decrement('memberships', 2)

Gauge is meant for static numbers that you want to track over time (as opposed to a rate for which you would use #count).

sensor.gauge('collection_count', Collection.count)

Logging can be used for tracking critical events. Valid log methods are info, warning, error, and success.

task :deploy do
  begin
    deploy!
    Seismograph::Log.info('App Deployed')
  rescue StandardError => e
    Seismograph::Log.error('Deployment failed!', description: e.message)
  end
end

To disable seismograph in your test environment, include this file in your test helper:

require 'seismograph/testing'

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request