instrumental_agent 0.1.2 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
data/README.rdoc CHANGED
@@ -8,29 +8,32 @@ Add the gem to your Gemfile.
8
8
 
9
9
  gem 'instrumental_agent'
10
10
 
11
- Head over to instrumentalapp.com and setup an account, then
12
- initialize the agent.
11
+ Visit instrumentalapp.com[instrumentalapp.com] and create an account, then
12
+ initialize the agent with your API key, found in the Docs section.
13
13
 
14
14
  I = Instrumental::Agent.new('YOUR_API_KEY', :enabled => Rails.env.production?)
15
15
 
16
- If you already use EventMachine elsewhere, or are hosted on heroku
17
- then you will need to disable the reactor loop startup like so:
16
+ If you're already using EventMachine elsewhere, or are hosted on Heroku, then you will need to disable the reactor loop startup.
18
17
 
19
18
  I = Instrumental::Agent.new('YOUR_API_KEY', :enabled => Rails.env.production?, :start_reactor => false)
20
19
 
21
- Now you can begin to use instrumental to track your application
20
+ Now you can begin to use Instrumental to track your application.
22
21
 
23
22
  I.gauge('load', 1.23)
24
23
  I.increment('signups')
25
24
 
26
- Data without historical context sucks, so Instrumental lets you
27
- backfill data to. Letting you see deep into your past.
25
+ Data without historical context sucks. Instrumental lets you
26
+ backfill data, allowing you to see deep into your project's past.
28
27
 
29
28
  User.find_each do |user|
30
29
  I.increment('signups', 1, user.created_at)
31
30
  end
32
31
 
33
- Running under Rails? You can also give our experimental rack middleware
32
+ Want some general server stats (load, memory, etc.)? Run this command, sorry not daemonized yet :)
33
+
34
+ instrument_server
35
+
36
+ Running under Rails? You can also give our experimental Rack middleware
34
37
  a shot by initializing it with:
35
38
 
36
- Instrumental::Middleware.boot
39
+ Instrumental::Middleware.boot
File without changes
@@ -1,4 +1,4 @@
1
1
  module Instrumental
2
- VERSION = "0.1.2"
2
+ VERSION = "0.1.3"
3
3
  end
4
4
 
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: instrumental_agent
3
3
  version: !ruby/object:Gem::Version
4
- hash: 31
4
+ hash: 29
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 1
9
- - 2
10
- version: 0.1.2
9
+ - 3
10
+ version: 0.1.3
11
11
  platform: ruby
12
12
  authors:
13
13
  - Elijah Miller
@@ -17,7 +17,7 @@ autorequire:
17
17
  bindir: bin
18
18
  cert_chain: []
19
19
 
20
- date: 2011-10-30 00:00:00 -04:00
20
+ date: 2011-10-31 00:00:00 -04:00
21
21
  default_executable:
22
22
  dependencies:
23
23
  - !ruby/object:Gem::Dependency
@@ -111,7 +111,7 @@ email:
111
111
  - netshade@gmail.com
112
112
  - kristopher.chambers@gmail.com
113
113
  executables:
114
- - watch_server.rb
114
+ - instrument_server
115
115
  extensions: []
116
116
 
117
117
  extra_rdoc_files: []
@@ -122,7 +122,7 @@ files:
122
122
  - Guardfile
123
123
  - README.rdoc
124
124
  - Rakefile
125
- - bin/watch_server.rb
125
+ - bin/instrument_server
126
126
  - instrumental_agent.gemspec
127
127
  - lib/instrumental/agent.rb
128
128
  - lib/instrumental/rack/middleware.rb