pingdom-to-graphite 0.0.4 → 0.0.5
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +22 -8
- data/lib/pingdom-to-graphite/version.rb +1 -1
- data/pingdom-to-graphite.gemspec +1 -1
- metadata +2 -2
data/README.md
CHANGED
@@ -6,42 +6,56 @@ place to prevent abuse. This tool tries to be mindful of that, although does
|
|
6
6
|
provide a "backfill" option if you care to burn up your daily api limit in one
|
7
7
|
fell swoop.
|
8
8
|
|
9
|
+
## Installation
|
10
|
+
|
11
|
+
pingdom-to-graphite is available as a gem package:
|
12
|
+
|
13
|
+
% gem install pingdom-to-graphite
|
14
|
+
% pingdom-to-graphite
|
15
|
+
|
16
|
+
Or, you could grab the source and call the executable directly:
|
17
|
+
|
18
|
+
% git clone git://github.com/lewg/pingdom-to-graphite.git
|
19
|
+
% cd pingdom-to-graphite
|
20
|
+
% bundle install
|
21
|
+
% bin/pingdom-to-graphite
|
22
|
+
|
9
23
|
## Usage
|
10
24
|
|
11
25
|
The utility itself will provide detailed help for all the commands if you just
|
12
26
|
invoke it by itself:
|
13
27
|
|
14
|
-
pingdom-to-graphite
|
28
|
+
% pingdom-to-graphite
|
15
29
|
|
16
30
|
### For the Impatient
|
17
31
|
|
18
32
|
Ok, so you don't like reading command line help. Here's how to get up and
|
19
33
|
running quickly:
|
20
34
|
|
21
|
-
pingdom-to-graphite init
|
35
|
+
% pingdom-to-graphite init
|
22
36
|
|
23
37
|
Will place a sample config file into the default location `~/.p2g/config.json`.
|
24
38
|
Don't worry scripters, this location can be overriden with the `-c` switch. Drop
|
25
39
|
your pingdom credentials and graphite settings into there to enable the script
|
26
40
|
to do any actual work.
|
27
41
|
|
28
|
-
pingdom-to-graphite init_checks
|
42
|
+
% pingdom-to-graphite init_checks
|
29
43
|
|
30
44
|
This will pre-fill the pingdom->checks setting in your config file with a list
|
31
45
|
of all your available check ids. Since you're curious:
|
32
46
|
|
33
|
-
pingdom-to-graphite list
|
47
|
+
% pingdom-to-graphite list
|
34
48
|
|
35
49
|
Will list them all, as well as their current status. Ok, back to business:
|
36
50
|
|
37
|
-
pingdom-to-graphite update
|
51
|
+
% pingdom-to-graphite update
|
38
52
|
|
39
53
|
Will pull the 100 most recent checks for each check specified in your config
|
40
54
|
file and create a `~/.p2g/state.json` file storing a few key timestamps about
|
41
55
|
what data you've successfully send to graphite. Similar to the config file, this
|
42
56
|
location can be overridden with the `-s` switch.
|
43
57
|
|
44
|
-
pingdom-to-graphite update
|
58
|
+
% pingdom-to-graphite update
|
45
59
|
|
46
60
|
*"Hey, that's the same command!"* you say. Indeed it is, and will run through your
|
47
61
|
checks picking up where we left of from the last update. If you stopped to check
|
@@ -53,7 +67,7 @@ limiting factor is that updating each metric is a separate API call, so the more
|
|
53
67
|
checks you want to pipe to graphite the less frequently you'll be able to run
|
54
68
|
the script. Want some numbers?
|
55
69
|
|
56
|
-
pingdom-to-graphite advice
|
70
|
+
% pingdom-to-graphite advice
|
57
71
|
|
58
72
|
Will give you the rough API numbers you'd consume a day given your number of
|
59
73
|
monitored checks in five minute increments until it finds something that works.
|
@@ -64,7 +78,7 @@ necessarily the best approach! Speaking of the API, how about some more historic
|
|
64
78
|
data because, you know, charts and stuff! Got that covered, but you're going to have
|
65
79
|
to pick the specific check you'd like some more data for.
|
66
80
|
|
67
|
-
pingdom-to-graphite
|
81
|
+
% pingdom-to-graphite backfill CHECK_ID
|
68
82
|
|
69
83
|
Will use up a number of your existing API calls to get historical data for that specific
|
70
84
|
check. How many? Well, it will ask, and you can tell it. You can also specify with the
|
data/pingdom-to-graphite.gemspec
CHANGED
@@ -7,7 +7,7 @@ Gem::Specification.new do |s|
|
|
7
7
|
s.version = PingdomToGraphite::VERSION
|
8
8
|
s.authors = ["Lew Goettner"]
|
9
9
|
s.email = ["lew@goettner.net"]
|
10
|
-
s.homepage = "
|
10
|
+
s.homepage = "https://github.com/lewg/pingdom-to-graphite"
|
11
11
|
s.summary = %q{A command line tool for pulling stats from pingdom and shipping them to graphite.}
|
12
12
|
s.description = %q{A tool for copying metrics from Pingdom to graphite. Pingdom, although
|
13
13
|
allowing access to effectively all your metrics through the API, does have some limits
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: pingdom-to-graphite
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.5
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -117,7 +117,7 @@ files:
|
|
117
117
|
- lib/pingdom-to-graphite/data-push.rb
|
118
118
|
- lib/pingdom-to-graphite/version.rb
|
119
119
|
- pingdom-to-graphite.gemspec
|
120
|
-
homepage:
|
120
|
+
homepage: https://github.com/lewg/pingdom-to-graphite
|
121
121
|
licenses: []
|
122
122
|
post_install_message:
|
123
123
|
rdoc_options: []
|