kingkong 0.0.1 → 0.0.2

data/Gemfile

@@ -4,4 +4,12 @@ source "http://rubygems.org"
 gemspec
 
 gem 'em-http-request'
-gem 'json'
+gem 'json'
+
+group :test, :development do
+  gem 'rspec'
+  gem 'guard-rspec'
+  gem 'growl'
+  gem 'rb-fsevent'
+  gem 'em-ventually'
+end

data/Guardfile

@@ -0,0 +1,5 @@
+guard 'rspec', :cli => '--color --format nested', :version => 2 do
+  watch(%r{^spec/.+_spec\.rb$})
+  watch(%r{^lib/(.+)\.rb$})     { |m| "spec/lib/#{m[1]}_spec.rb" }
+  watch('spec/spec_helper.rb')  { "spec/" }
+end

data/README.md

@@ -8,7 +8,7 @@
          | /.----/ O O \----.\ |       
           \/     |     |     \/        
           |                   |            
-          |                   |           
+          |                   |           KingKong gets what KingKong wants!
           |                   |          
           _\   -.,_____,.-   /_         
       ,.-"  "-.,_________,.-"  "-.,
@@ -26,8 +26,34 @@
        /"-.,__,.-"\   /"-.,__,.-"\"-.,_,.-"\
       |            \ /            |         |
       |             |             |         |
-       \__|__|__|__/ \__|__|__|__/ \_|__|__/ KingKong gets what KingKong wants!
+       \__|__|__|__/ \__|__|__|__/ \_|__|__/
 
 KingKong makes it easy to build full-stack ping-pong checks. You might need this to check and graph out the response time on your website, Twitter application, SMS gateway, or whatever else you'd connect to a network.
 
+When its done, it will look something like this:
+
+    KingKing.monitor {
+      socket '/tmp/kingkong.socket' # Munin can check this for stats
+
+      ping(:google).every(3).seconds do |ping|
+        google = http('http://www.google.com/').get
+
+        ping.on_timeout {
+          # ZOMG! Email the admin! Google is down!
+        }
+
+        ping.start_time           # Start the clock!
+        google.callback {         # This triggers the request
+          ping.end_time           # And this stops the clock!
+        }
+      end
+
+      ping(:twitter).every(10).seconds do |ping|
+        # Wire up your own thing in here that tweets
+        # .. and when you pick that up, end the pong!
+      end
+    }
+
+and its going to aggregate stats so you can plug it into munin and get all sorts of graphing goodness.
+
 Stay tuned, I'm still working out the ping DSL and reporting infrastructure!

data/Rakefile

@@ -1 +1,4 @@
-require "bundler/gem_tasks"
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)

data/lib/kingkong.rb

@@ -2,7 +2,17 @@ require "kingkong/version"
 
 module KingKong
   autoload :Ping,       'kingkong/ping'
+  autoload :Pinger,     'kingkong/pinger'
   autoload :Server,     'kingkong/server'
   autoload :Logging,    'kingkong/logging'
   autoload :Aggregator, 'kingkong/aggregator'
+
+  # Default logger for KingKong.
+  def self.logger
+    @logger ||= Logger.new($stdout)
+  end
+
+  def self.logger=(logger)
+    @logger = logger
+  end
 end

data/lib/kingkong/aggregator.rb

@@ -4,7 +4,7 @@ module KingKong
   class Aggregator
     attr_reader :sum, :max_count, :pings, :started_at
 
-    def initialize(max_count=10)
+    def initialize(max_count=10_000)
       @max_count = max_count
       reset
     end
@@ -48,7 +48,7 @@ module KingKong
 
     # Reset all of the counts to 0 and empty all of the pings
     def reset
-      @sum        = 0
+      @sum        = 0.0
       @pings      = Array.new
       @started_at = Time.now
     end

data/lib/kingkong/logging.rb

@@ -7,9 +7,4 @@ module KingKong
       KingKong.logger
     end
   end
-
-  # Default logger for KingKong.
-  def self.logger
-    @logger ||= Logger.new($stdout)
-  end
 end

data/lib/kingkong/pinger.rb

@@ -0,0 +1,53 @@
+require 'eventmachine'
+
+module KingKong
+  class Pinger
+    include Logging
+
+    attr_accessor :aggregator, :duration
+
+    def initialize(duration=5)
+      @duration = duration
+    end
+
+    # Starts the pinger
+    def start(&block)
+      logger.debug "Starting pinger #{self}"
+      @timer = EventMachine::PeriodicTimer.new(duration){ ping(&block) }
+      ping(&block)
+    end
+
+    # Stop the pinger from executing
+    def stop
+      logger.debug "Stopping pinger #{self}"
+      @timer.cancel if @timer
+    end
+
+    # Gather up all the numbers we need for reporting later on
+    def aggregator
+      @aggregatore ||= Aggregator.new
+    end
+    
+  private
+    # Add all of the instrumentation callbacks into the ping so we can aggregate it later
+    def ping(&block)
+      ping = Ping::Deferrable.new(30, sequencer)
+      # Register the aggregator to process the ping
+      ping.callback { 
+        logger.debug "Ping #{ping} successful"
+        aggregator.process ping
+      }
+      ping.errback  {
+        logger.debug "Ping #{ping} error (probably a timeout)"
+        aggregator.process ping
+      }
+      # Now pass the ping into the block so we can start/stop it
+      yield ping if block_given?
+    end
+
+    # Setup a squencer that's unique specifically to this pinger
+    def sequencer
+      @sequencer ||= Ping::Sequencer.new
+    end
+  end
+end

data/lib/kingkong/version.rb

@@ -1,3 +1,3 @@
 module KingKong
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

data/spec/lib/kingkong/pinger_spec.rb

@@ -0,0 +1,19 @@
+require 'spec_helper'
+
+describe KingKong::Pinger do
+    include EM::Ventually
+
+    before(:all) do
+      @pinger = KingKong::Pinger.new
+    end
+
+    it "should start pinging" do
+      @pinger.start
+    end
+
+    it "should stop pinging" do
+      @pinger.stop
+    end
+
+    it "should sequence pings"
+end

data/spec/lib/kingkong_spec.rb

@@ -0,0 +1,4 @@
+require 'spec_helper'
+
+describe KingKong do
+end

data/spec/spec_helper.rb

@@ -0,0 +1,8 @@
+require 'bundler/setup'
+require 'kingkong'
+require 'eventmachine'
+require 'logger'
+require 'em-ventually'
+
+# Squelch the logger so we can see our specs passing
+KingKong.logger = Logger.new('/dev/null')

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kingkong
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2011-09-02 00:00:00.000000000Z
+date: 2011-09-06 00:00:00.000000000Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: eventmachine
-  requirement: &70132736057580 !ruby/object:Gem::Requirement
+  requirement: &70207424167020 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,7 +21,7 @@ dependencies:
         version: '0'
   type: :runtime
   prerelease: false
-  version_requirements: *70132736057580
+  version_requirements: *70207424167020
 description: Have you ever wanted to shoot a message throught Twitter, have your app
   pick it up, do some work on it, and report how long it takes? KingKong makes it
   slightly easier to do this with a DSL for writing custom pings and by providing
@@ -37,19 +37,23 @@ files:
 - .gitignore
 - .rvmrc
 - Gemfile
+- Guardfile
 - README.md
 - Rakefile
 - bin/kingkong-munin
 - bin/kingkong-server
 - kingkong.gemspec
-- lib/README.md
 - lib/kingkong.rb
 - lib/kingkong/aggregator.rb
 - lib/kingkong/cli.rb
 - lib/kingkong/logging.rb
 - lib/kingkong/ping.rb
+- lib/kingkong/pinger.rb
 - lib/kingkong/server.rb
 - lib/kingkong/version.rb
+- spec/lib/kingkong/pinger_spec.rb
+- spec/lib/kingkong_spec.rb
+- spec/spec_helper.rb
 homepage: ''
 licenses: []
 post_install_message: 
@@ -74,4 +78,7 @@ rubygems_version: 1.8.6
 signing_key: 
 specification_version: 3
 summary: Build complex network application health checks with Ruby and EventMachine
-test_files: []
+test_files:
+- spec/lib/kingkong/pinger_spec.rb
+- spec/lib/kingkong_spec.rb
+- spec/spec_helper.rb

data/lib/README.md

@@ -1,33 +0,0 @@
-# KingKong
-
-                ,.-" "-.,
-               /   ===   \
-              /  =======  \
-           __|  (o)   (0)  |__      
-          / _|    .---.    |_ \         
-         | /.----/ O O \----.\ |       
-          \/     |     |     \/        
-          |                   |            
-          |                   |           KingKong gets what KingKong wants!
-          |                   |          
-          _\   -.,_____,.-   /_         
-      ,.-"  "-.,_________,.-"  "-.,
-     /          |       |          \  
-    |           l.     .l           | 
-    |            |     |            |
-    l.           |     |           .l             
-     |           l.   .l           | \,     
-     l.           |   |           .l   \,    
-      |           |   |           |      \,  
-      l.          |   |          .l        |
-       |          |   |          |         |
-       |          |---|          |         |
-       |          |   |          |         |
-       /"-.,__,.-"\   /"-.,__,.-"\"-.,_,.-"\
-      |            \ /            |         |
-      |             |             |         |
-       \__|__|__|__/ \__|__|__|__/ \_|__|__/
-
-KingKong makes it easy to build full-stack ping-pong checks. You might need this to check and graph out the response time on your website, Twitter application, SMS gateway, or whatever else you'd connect to a network.
-
-Stay tuned, I'm still working out the ping DSL and reporting infrastructure!