Sha256: 27751acab20c404055807a2870168087a992feda381f84130e2d3964939533dd
Contents?: true
Size: 1.24 KB
Versions: 1
Compression:
Stored size: 1.24 KB
Contents
= Instrumental Agent Instrument anything. == Setup & Usage Add the gem to your Gemfile. gem 'instrumental_agent' Visit instrumentalapp.com[instrumentalapp.com] and create an account, then initialize the agent with your API key, found in the Docs section. I = Instrumental::Agent.new('YOUR_API_KEY', :enabled => Rails.env.production?) If you're already using EventMachine elsewhere, or are hosted on Heroku, then you will need to disable the reactor loop startup. I = Instrumental::Agent.new('YOUR_API_KEY', :enabled => Rails.env.production?, :start_reactor => false) Now you can begin to use Instrumental to track your application. I.gauge('load', 1.23) I.increment('signups') Data without historical context sucks. Instrumental lets you backfill data, allowing you to see deep into your project's past. User.find_each do |user| I.increment('signups', 1, user.created_at) end Want some general server stats (load, memory, etc.)? Run this command, sorry not daemonized yet :) instrument_server Running under Rails? You can also give our experimental Rack middleware a shot by initializing it with: Instrumental::Middleware.boot == Troubleshooting & Help We are here to help, please email us at support@instrumentalapp.com.
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
instrumental_agent-0.1.4 | README.rdoc |