grape-librato's Introduction

Librato::Grape

Librato tracking for Grape, based on code from this NewRelic gem, using librato-rack

Installation

Add this line to your application's Gemfile:

gem 'grape-librato'

Or install:

$ gem install grape-librato

Include it in your Grape API like this

class TestAPI < Grape::API
  use Librato::Grape::Middleware

  get 'hello' do
    "Hello World"
  end
end

Make sure you are also using the librato-rack middleware

Here's an example config.ru

require 'grape'
require 'librato-rack'
require 'grape-librato'

LIBRATO_CONFIGURATION        = Librato::Rack::Configuration.new
LIBRATO_CONFIGURATION.user   = ENV['LIBRATO_USER']
LIBRATO_CONFIGURATION.token  = ENV['LIBRATO_TOKEN']
LIBRATO_CONFIGURATION.source = ENV['LIBRATO_SOURCE'] || 'localhost'

class API < Grape::API
  use Librato::Grape::Middleware
  get 'hello' do
    "Hello World"
  end
end

use Librato::Rack, config: LIBRATO_CONFIGURATION
run API

See how to set up the Librato::Rack object in the librato-rack documentation.

Contributing

Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Make a pull request

grape-librato's People

Contributors

Stargazers

Watchers

grape-librato's Issues

Default metric name?

The current default metric name yields something like GET.hello.:name when your route is specified as get 'hello/:name'.

This name seems to be playing nice with Librato (it didn't like having spaces), but I'm not sure if there's a better standard way to make a metric name from a route. Happy to hear any suggestions.

Recommend Projects