rubix 0.5.6 → 0.5.7

data/README.rdoc

@@ -1,30 +1,17 @@
 = Rubix
 
-Rubix is a Ruby client for Zabbix[http://www.zabbix.com/].  It has a
-few goals:
+Rubix is a Ruby client for Zabbix[http://www.zabbix.com/] that makes
+it easier to programatically control Zabbix resources so that they can
+be coordinated in complex, dynamic, and distributed environments like
+clouds.
 
-- Provide a +Connection+ and +Response+ class that abstract away the
-  complexity[http://www.zabbix.com/documentation/1.8/api/getting_started]
-  of authenticating with and sending API requests to Zabbix.
+Rubix provides a wrapper for the {Zabbix API
+documentation}[http://www.zabbix.com/documentation/1.8/api] and an ORM
+for resources like Hosts, HostGroups, Templates, Items, &c.
 
-- Provide an ORM for Zabbix resources like Hosts, HostGroups,
-  Templates, &c. using the {Zabbix
-  API}[http://www.zabbix.com/documentation/1.8/api].
+Rubix also provides simple command line tools and Ruby classes that
+make it easier to query Zabbix and send it data.
 
-- Provide a command-line script that wraps the
-  {+zabbix_sender+}[http://www.zabbix.com/documentation/1.8/manpages/zabbix_sender]
-  utility, allowing it to consume JSON data and to 'auto-vivify'
-  hosts, hostgroups, applications, and items.
-
-- Provide some +Monitor+ classes that make it easy to write scripts
-  that periodically measure something and push it to Zabbix.
-
-- Have as few dependencies as possible: the core classes only depend
-  on Ruby 1.8 standard library & +JSON+ and scripts additionally
-  depend on +Configliere+[http://github.com/mrflip/configliere].
-
-- Play nicely with Chef[http://www.opscode.com/chef/]  
-  
 There are a lot of other projects out there that connect Ruby to
 Zabbix.  Here's a quick list:
 
@@ -56,20 +43,17 @@ zabbix-web[http://github.com/legiar/zabbix-web]::
 zabcon[http://trac.red-tux.net/]::
   Zabcon is a command line interface for Zabbix written in Ruby
 
-None of these projects was satisfactory for our purposes so I decided
-to write Rubix.  The name is terrible but the code is better.  Enjoy!
-
 == Connections, Requests, & Responses
 
-Getting connected is easy
+Getting connected to the Zabbix API is easy
 
   require 'rubix'
 
   # Provide API URL & credentials.  These are the defaults.
   Rubix.connect('http://localhost/api_jsonrpc.php', 'admin', 'zabbix')
 
-As per the {Zabbixi API
-documentation}[http://www.zabbix.com/documentation/1.8/api], each
+As per the {Zabbix API
+documentation}[http://www.zabbix.com/documentation/1.8/api] each
 request to the Zabbix API needs four values:
 
 +id+::
@@ -116,6 +100,18 @@ issue these sorts of requests directly on the command line.
 +zabbix_api+ lets you specify the credentials and will pretty-print
 responses for you.  Try <tt>zabbix_api --help</tt> for more details.
 
+=== Logging
+
+Rubix produces log messages at the <tt>Logger::INFO</tt> level to a
++Logger+ instance by default.  When the logger severity is
+<tt>Logger::DEBUG</tt> Rubix will log the request and response to
+every API call it makes against the Zabbix API.  This can be useful
+when debugging why a particular interaction isn't working as expected.
+
+Besides programatically modifying the logger, the log level and path
+can be modified at runtime with the environment variables
++RUBIX_LOG_LEVEL+ and +RUBIX_LOG_PATH+.
+
 == ORM
 
 If you don't want to deal with the particulars of the Zabbix API
@@ -146,125 +142,8 @@ complete with host groups, templates, applications, and so on.
   item = Rubix::Item.new(:host => host, :key => 'foo.bar.baz', :description => "Some Item", :value_type => :unsigned_int, :applications => [app])
   item.save
 
-You can also +update+ and +destroy+ resources.
-
-Only host groups, templates, hosts, applications, user macros, and
-items are available at present.  Other Zabbix resources (actions,
-alerts, events, maps, users, &c.) can be similarly wrapped, they just
-haven't been yet because we don't use them as much as we use these
-core resources.
-
-== Sender
-
-Rubix comes with a +zabbix_pipe+ script which, coupled with the
-{+zabbix_sender+}[http://www.zabbix.com/documentation/1.8/manpages/zabbix_sender]
-utility, allows for writing data to Zabbix.
-
-By the design of Zabbix, all data written via +zabbix_sender+ (and
-therefore +zabbix_pipe+) must be written to items with type "Zabbix
-trapper".  This type instructs Zabbix to accept values written by
-+zabbix_sender+.
-
-+zabbix_pipe+ can consume data from +STDIN+, a file on disk, or a
-{named pipe}[http://en.wikipedia.org/wiki/Named_pipe].  It consumes
-data one line at a time from any of these sources and uses the
-+zabbix_sender+ utility to send this data to a Zabbix server.
-
-Here's an example of starting +zabbix_pipe+ and sending some data onto
-Zabbix.  (Credentials and addresses for the Zabbix server and the
-Zabbix API can all be customized; see the <tt>--help</tt> option.)
-
-  # Send one data point -- this is tab separated!
-  $ echo "foo.bar.baz	123" | zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
-  # Send a bunch of data points in a file
-  $ cat my_data.tsv | zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
-
-You can also pass the file directly:
-
-  # Send a bunch of data points in a file
-  $ zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group' my_data.tsv
-
-You can also listen from a named pipe.  This is useful on a
-"production" system in which many processes may want to simply and
-easily write somewhere without worrying about what happens.
-
-  # In the first terminal
-  $ mkfifo /dev/zabbix
-  $ zabbix_pipe --pipe=/dev/zabbix --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
-
-  # In another terminal
-  $ echo "foo.bar.baz	123" > /dev/zabbix
-  $ cat my_data > /dev/zabbix
-
-In any of these modes, you can also send JSON data directly.
-
-  $ echo '{"data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
-
-This simple block of JSON doesn't really add any power to
-+zabbix_pipe+.  What becomes more interesting is that we can wedge in
-data for *diffferent* hosts, items, &c. when using JSON input:
-
-  $ echo '{"host": "My first host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
-  $ echo '{"host": "My second host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
-  $ echo '{"host": "My third host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
-
-Rubix will switch hosts on the fly.
-
-=== Auto-vivification
-
-By default, for every item written into +zabbix_pipe+, Rubix will
-first check, using the Zabbix API, whether an item with the given key
-exists for the given host.  If not, Rubix will create the host and
-the item.  You can pass a few details along with your data (when
-writing in JSON format) or at startup of the +zabbix_pipe+ to tune
-some of the properites of newly created hosts and items:
-
-  $ echo '{"host": "My host", "hostgroups": "Host Group 1,Host Group 2", "templates": "Template 1,Template 2", "applications": "App 1, App2", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
-
-If the host 'My host' does not exist, Rubix will create it, putting in
-each of the host groups 'Host Group 1' and 'Host Group 2' (which will
-also be auto-vivified), and attach it to templates 'Template 1' and
-'Template 2' (auto-vivified).  If the item does not exist for the host
-'My host', then it will be created and put inside applications 'App1'
-and 'App2' (auto-vivified).  The value type of the item (unsigned int,
-float, character, text, &c.) will be chosen dynamically based on the
-value being written. The created items will all be of the type "Zabbix
-trapper" so that they can be written to.
-
-Auto-vivification is intended to make it easy to register a lot of
-dynamic hosts and items in Zabbix.  This is perfect for cloud
-deployments where resources to be monitored are often dynamic.
-
-==== Failed writes
-
-By the design of Zabbix, a newly created item of type 'Zabbix trapper'
-will not accept data for some interval, typically a minute or so,
-after being created.  This means that when writing a series of values
-for some non-existent item 'foo.bar.baz', the first write will cause
-the item to be created (auto-vivified), the next several writes will
-fail as the Zabbix server is not accepting writes for this item yet,
-and then all writes will begin to succeed as the Zabbix server catches
-up.  If it is absolutely essential for all writes to succeed,
-including the first, then +zabbix_pipe+ needs to go to sleep for a
-while after creating a new item in order to give the Zabbix server
-time to catch up.  This can be configured with the
-<tt>--create_item_sleep</tt> option.  By default this is set to 0.
-
-==== Skipping auto-vivification
-
-Attempting to auto-vivify keys on every single write is expensive and
-does not scale.  It's recommended, therefore, to run +zabbix_pipe+
-with the <tt>--fast</tt> flag in production settings.  In this mode,
-+zabbix_pipe+ will not attempt to auto-vivify anything -- if items do
-not exist, writes will just fail, as they do with +zabbix_sender+
-itself.
-
-A good pattern is to set up a production pipe (in <tt>--fast</tt>)
-mode at <tt>/dev/zabbix</tt> and to do all development/deployment with
-a separate instance of +zabbix_pipe+.  Once development/deployment is
-complete and all hosts, groups, templates, applications, and items
-have been created, switch to writing all data in "production mode"
-using the <tt>--fast</tt> pipe at <tt>/dev/zabbix</tt>.
+You can also +update+ and +destroy+ resources as well as probe
+associations: <tt>host.items</tt>.
 
 == Monitors
 
@@ -288,66 +167,23 @@ used memory in bytes.
 
   MemoryMonitor.run if $0 == __FILE__
 
-The file <tt>memory_monitor.rb</tt> can now be run on the command line in
-various ways:
+The file <tt>memory_monitor.rb</tt> can now be run on the command line
+in various ways.  Most simply it will just output a measurement.
 
-  # Write the output to STDOUT
   $ ruby memory_monitor.rb
   'mem.used'	11595908
 
-  # Loop every 30 seconds
-  $ ruby memory_monitor.rb --loop=30
+You can also have it loop after a number of seconds
 
+  $ ruby memory_monitor.rb --loop=30
   'mem.used'	11595760
   'mem.used'	11595800
   'mem.used'	11596016
   'mem.used'	11596008
 
-It can be piped into a running +zabbix_pipe+:
-
-  $ ruby memory_monitor.rb --loop=30 > /dev/zabbix &
-
-=== Monitors with Chef
-
-It's useful to be able to monitor resources defined in
-Chef[http://www.opscode.com/chef/] and so Rubix comes with a
-+ChefMonitor+ class.
-
-  # in webserver_monitor.rb
-  require 'rubix'
-  require 'net/http'
-  require 'uri'
-  
-  class WebserverMonitor < Rubix::ChefMonitor
-
-    def webserver
-      @webserver ||= chef_node_from_node_name('my_webserver')
-    end
-
-    def uri
-      URI.parse("http://#{webserver['ec2']['public_hostname']}")
-    end
-  
-    def measure
-      begin
-        if Net::HTTP.get_response(uri).code.to_i == 200
-          availability = 1
-        else
-          availability = 0
-	end
-      rescue => e
-        availability = 0
-      end
-      write do |data|
-        data << ([['webserver.available', availability]])
-      end
-    end
-  end
-
-  WebserverMonitor.run if $0 == __FILE__
-
-To run this monitor you'll have to pass in credentials used to authenticate with Chef:
+You can pipe the results directly to Zabbix (uses {Zabbix
+sender}[http://www.zabbix.com/documentation/1.8/manual/processes/zabbix_sender]
+behind the scenes):
 
-  $ sudo ruby webserver_monitor.rb --chef_server_url=http://api.opscode.com/organizations/my_company --chef_node_name=this_node --chef_client_key=/etc/chef/client.pem --loop=30 > /dev/zabbix
+  $ ruby memory_monitor.rb --loop=30 --send
 
-Make sure you can read the file at <tt>/etc/chef/client.pem</tt>!

data/VERSION

@@ -1 +1 @@
-0.5.6
+0.5.7

data/lib/rubix.rb

@@ -69,6 +69,17 @@ module Rubix
     @connection
   end
 
+  # Return the current Rubix version.
+  #
+  # @return [String]
+  def self.version
+    @version ||= begin
+      File.read(File.expand_path('../../VERSION', __FILE__)).chomp
+    rescue => e
+      'unknown'
+    end    
+  end
+
   # Base class for Rubix errors.
   Error               = Class.new(RuntimeError)
 

data/lib/rubix/auto_sender.rb

@@ -2,27 +2,118 @@ require 'rubix/log'
 
 module Rubix
 
-  # A class used to send data to Zabbix.
+  # == Sender
   #
-  # This sender is used to implement the logic for the +zabbix_pipe+
-  # utility.  It is initialized with some metadata about a host, its
-  # host groups and templates, and applications into which items
-  # should be written, and it can then accept data and forward it to a
-  # Zabbix server using the +zabbix_sender+ utility that comes with
-  # Zabbix.
+  # Rubix comes with a +zabbix_pipe+ script which, coupled with the
+  # {+zabbix_sender+}[http://www.zabbix.com/documentation/1.8/manpages/zabbix_sender]
+  # utility, allows for writing data to Zabbix.
   #
-  # A sender can be given data in either TSV or JSON formats.  With
-  # the JSON format, it is possible to embed data for hosts, host
-  # groups, &c. distinct from that with which this sender was
-  # initialized.  This is a useful way to send many different kinds of
-  # data through the same process.
+  # By the design of Zabbix, all data written via +zabbix_sender+ (and
+  # therefore +zabbix_pipe+) must be written to items with type "Zabbix
+  # trapper".  This type instructs Zabbix to accept values written by
+  # +zabbix_sender+.
   #
-  # The sender will also auto-vivify any hosts, host gruops,
-  # templates, applications, and items it needs in order to be able to
-  # write data.  This is expensive in terms of time so it can be
-  # turned off using the <tt>--fast</tt> option.
+  # +zabbix_pipe+ can consume data from +STDIN+, a file on disk, or a
+  # {named pipe}[http://en.wikipedia.org/wiki/Named_pipe].  It consumes
+  # data one line at a time from any of these sources and uses the
+  # +zabbix_sender+ utility to send this data to a Zabbix server.
+  #
+  # Here's an example of starting +zabbix_pipe+ and sending some data onto
+  # Zabbix.  (Credentials and addresses for the Zabbix server and the
+  # Zabbix API can all be customized; see the <tt>--help</tt> option.)
+  #
+  #   # Send one data point -- this is tab separated!
+  #   $ echo "foo.bar.baz	123" | zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
+  #   # Send a bunch of data points in a file
+  #   $ cat my_data.tsv | zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
+  #
+  # You can also pass the file directly:
+  #
+  #   # Send a bunch of data points in a file
+  #   $ zabbix_pipe --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group' my_data.tsv
+  #
+  # You can also listen from a named pipe.  This is useful on a
+  # "production" system in which many processes may want to simply and
+  # easily write somewhere without worrying about what happens.
+  #
+  #   # In the first terminal
+  #   $ mkfifo /dev/zabbix
+  #   $ zabbix_pipe --pipe=/dev/zabbix --host='My Zabbix Host' --host_groups='My Zabbix Servers,Some Other Group'
+  #
+  #   # In another terminal
+  #   $ echo "foo.bar.baz	123" > /dev/zabbix
+  #   $ cat my_data > /dev/zabbix
+  #
+  # In any of these modes, you can also send JSON data directly.
+  #
+  #   $ echo '{"data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
+  #
+  # This simple block of JSON doesn't really add any power to
+  # +zabbix_pipe+.  What becomes more interesting is that we can wedge in
+  # data for *diffferent* hosts, items, &c. when using JSON input:
+  #
+  #   $ echo '{"host": "My first host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
+  #   $ echo '{"host": "My second host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
+  #   $ echo '{"host": "My third host", "host_groups": "My Zabbix Servers,Some Other Group", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
+  #
+  # Rubix will switch hosts on the fly.
+  #
+  # === Auto-vivification
+  #
+  # By default, for every item written into +zabbix_pipe+, Rubix will
+  # first check, using the Zabbix API, whether an item with the given key
+  # exists for the given host.  If not, Rubix will create the host and
+  # the item.  You can pass a few details along with your data (when
+  # writing in JSON format) or at startup of the +zabbix_pipe+ to tune
+  # some of the properites of newly created hosts and items:
+  #
+  #   $ echo '{"host": "My host", "hostgroups": "Host Group 1,Host Group 2", "templates": "Template 1,Template 2", "applications": "App 1, App2", "data": [{"key": "foo.bar.baz", "value": 123}, {"key": "foo.bar.baz", "value": 101}]}' > /dev/zabbix
+  #
+  # If the host 'My host' does not exist, Rubix will create it, putting in
+  # each of the host groups 'Host Group 1' and 'Host Group 2' (which will
+  # also be auto-vivified), and attach it to templates 'Template 1' and
+  # 'Template 2' (auto-vivified).  If the item does not exist for the host
+  # 'My host', then it will be created and put inside applications 'App1'
+  # and 'App2' (auto-vivified).  The value type of the item (unsigned int,
+  # float, character, text, &c.) will be chosen dynamically based on the
+  # value being written. The created items will all be of the type "Zabbix
+  # trapper" so that they can be written to.
+  #
+  # Auto-vivification is intended to make it easy to register a lot of
+  # dynamic hosts and items in Zabbix.  This is perfect for cloud
+  # deployments where resources to be monitored are often dynamic.
+  #
+  # ==== Failed writes
+  #
+  # By the design of Zabbix, a newly created item of type 'Zabbix trapper'
+  # will not accept data for some interval, typically a minute or so,
+  # after being created.  This means that when writing a series of values
+  # for some non-existent item 'foo.bar.baz', the first write will cause
+  # the item to be created (auto-vivified), the next several writes will
+  # fail as the Zabbix server is not accepting writes for this item yet,
+  # and then all writes will begin to succeed as the Zabbix server catches
+  # up.  If it is absolutely essential for all writes to succeed,
+  # including the first, then +zabbix_pipe+ needs to go to sleep for a
+  # while after creating a new item in order to give the Zabbix server
+  # time to catch up.  This can be configured with the
+  # <tt>--create_item_sleep</tt> option.  By default this is set to 0.
+  #
+  # ==== Skipping auto-vivification
+  #
+  # Attempting to auto-vivify keys on every single write is expensive and
+  # does not scale.  It's recommended, therefore, to run +zabbix_pipe+
+  # with the <tt>--fast</tt> flag in production settings.  In this mode,
+  # +zabbix_pipe+ will not attempt to auto-vivify anything -- if items do
+  # not exist, writes will just fail, as they do with +zabbix_sender+
+  # itself.
+  #
+  # A good pattern is to set up a production pipe (in <tt>--fast</tt>)
+  # mode at <tt>/dev/zabbix</tt> and to do all development/deployment with
+  # a separate instance of +zabbix_pipe+.  Once development/deployment is
+  # complete and all hosts, groups, templates, applications, and items
+  # have been created, switch to writing all data in "production mode"
+  # using the <tt>--fast</tt> pipe at <tt>/dev/zabbix</tt>.
   class AutoSender
-
     include Logs
 
     # @return [Hash] settings

data/lib/rubix/connection.rb

@@ -159,6 +159,11 @@ module Rubix
     # restarting or something like that.  We keep trying until that
     # doesn't happen.
     #
+    # During long-running connections, the Zabbix server can reap the
+    # existing session if some time has passed since the last request
+    # from this Connection.  This method will also refresh the
+    # connection in that instance.
+    #
     # You shouldn't have to use this method directly -- the
     # <tt>Rubix::Connection#authorize!</tt> and
     # <tt>Rubix::Connection#request</tt> methods already use this
@@ -172,6 +177,9 @@ module Rubix
         till_response(attempt + 1, max_attempts, &block)
       when response.code.to_i >= 500
         raise ConnectionError.new("Too many consecutive failed requests (#{max_attempts}) to the Zabbix API at (#{uri}).")
+      when response.code.to_i == 200 && authorized? && response.body =~ /-32602/ && response.body =~ /Not authorized/
+        authorize!
+        till_response(attempt, max_attempts, &block)
       else
         @last_response = response
       end
@@ -221,6 +229,7 @@ module Rubix
       Rubix.logger.log(Logger::DEBUG, "SEND: #{json_body}") if Rubix.logger
       Net::HTTP::Post.new(uri.path).tap do |req|
         req['Content-Type'] = 'application/json-rpc'
+        req['User-Agent']   = "Rubix v. #{Rubix.version}"
         req.body            = json_body
       end
     end

data/lib/rubix/monitors/monitor.rb

@@ -67,7 +67,7 @@ module Rubix
         s.define :port,   :description => "Port of a Zabbix server",                             :required => false, :default => 10051, :type => Integer
         s.define :host,   :description => "Name of a Zabbix host",                               :required => false, :default => ENV["HOSTNAME"]
         s.define :config, :description => "Local Zabbix agentd configuration file",              :required => false, :default => "/etc/zabbix/zabbix_agentd.conf"
-        s.define :send,   :description => "Send data directlyt to Zabbix using 'zabbix_sender'", :required => false, :default => false, :type => :boolean
+        s.define :send,   :description => "Send data directly to Zabbix using 'zabbix_sender'",  :required => false, :default => false, :type => :boolean
       end
     end
 

data/spec/rubix/connection_spec.rb

@@ -41,6 +41,12 @@ describe Rubix::Connection do
       @connection.request_id.should == 3 # it's the number used for the *next* request
     end
 
+    it "should refresh its authorization credentials if they are deleted automatically" do
+      @mock_response.stub!(:body).and_return('{"jsonrpc":"2.0","error":{"code":-32602,"message":"Invalid params.","data":"Not authorized"},"id":4}')
+      @connection.should_receive(:authorize!)
+      @connection.request('foobar', {})
+    end
+
   end
 
   describe "sending web requests" do

data/spec/support/integration_helper.rb

@@ -79,7 +79,7 @@ module Rubix
         $RUBIX_MYSQL.query(%Q{INSERT INTO users_groups (usrgrpid, userid)                       SELECT users.userid, usrgrp.usrgrpid FROM users, usrgrp WHERE users.alias = '#{INTEGRATION_USER}' AND usrgrp.name = '#{INTEGRATION_GROUP}'})
         true
       rescue => e
-        puts "Could not create integraiton user or group: #{e.class} -- #{e.message}"
+        puts "Could not create integration user or group: #{e.class} -- #{e.message}"
         puts e.backtrace
         false
       end

data/spec/test.yml

@@ -1,11 +1,11 @@
 ---
-  
+
 api:
-  url: http://127.0.0.1:5000/~huston/php/api_jsonrpc.php
-  username: Admin
-  password: zabbix
+  url: localhost:8080/api_jsonrpc.php
+
 mysql:
-  host: 127.0.0.1
-  username: root
+  host: localhost
+  username: dhruv
   password: 
-  database: zabbix
+  database: zabbix
+  

metadata

@@ -1,194 +1,214 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: rubix
-version: !ruby/object:Gem::Version 
+version: !ruby/object:Gem::Version
+  version: 0.5.7
   prerelease: 
-  version: 0.5.6
 platform: ruby
-authors: 
+authors:
 - Dhruv Bansal
 autorequire: 
 bindir: bin
 cert_chain: []
-
-date: 2012-06-12 00:00:00 Z
-dependencies: 
-- !ruby/object:Gem::Dependency 
+date: 2012-07-18 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
   name: rspec
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
+  requirement: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :development
-  version_requirements: *id001
-- !ruby/object:Gem::Dependency 
-  name: mysql2
   prerelease: false
-  requirement: &id002 !ruby/object:Gem::Requirement 
+  version_requirements: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: mysql2
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :development
-  version_requirements: *id002
-- !ruby/object:Gem::Dependency 
-  name: json
   prerelease: false
-  requirement: &id003 !ruby/object:Gem::Requirement 
+  version_requirements: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: json
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
     - - <=
-      - !ruby/object:Gem::Version 
+      - !ruby/object:Gem::Version
         version: 1.6.1
   type: :runtime
-  version_requirements: *id003
-- !ruby/object:Gem::Dependency 
-  name: configliere
   prerelease: false
-  requirement: &id004 !ruby/object:Gem::Requirement 
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - <=
+      - !ruby/object:Gem::Version
+        version: 1.6.1
+- !ruby/object:Gem::Dependency
+  name: configliere
+  requirement: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
         version: 0.4.8
   type: :runtime
-  version_requirements: *id004
-- !ruby/object:Gem::Dependency 
-  name: multipart-post
   prerelease: false
-  requirement: &id005 !ruby/object:Gem::Requirement 
+  version_requirements: !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 0.4.8
+- !ruby/object:Gem::Dependency
+  name: multipart-post
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
   type: :runtime
-  version_requirements: *id005
-description: Rubix provides abstractions for connecting to Zabbix's API, an ORM for wrapping Zabbix resources, a set of scripts for writing data to Zabbix, and a collection of Monitor classes for building periodic monitors.
-email: 
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Rubix provides abstractions for connecting to Zabbix's API, an ORM for
+  wrapping Zabbix resources, a set of scripts for writing data to Zabbix, and a collection
+  of Monitor classes for building periodic monitors.
+email:
 - dhruv@infochimps.com
-executables: 
+executables:
 - zabbix_api
 - zabbix_pipe
 extensions: []
-
 extra_rdoc_files: []
-
-files: 
+files:
 - bin/zabbix_api
 - bin/zabbix_pipe
-- lib/rubix/associations/belongs_to_action.rb
-- lib/rubix/associations/belongs_to_host.rb
-- lib/rubix/associations/belongs_to_item.rb
+- lib/rubix.rb
+- lib/rubix/models/template.rb
+- lib/rubix/models/trigger.rb
+- lib/rubix/models/media_type.rb
+- lib/rubix/models/user_macro.rb
+- lib/rubix/models/action.rb
+- lib/rubix/models/script.rb
+- lib/rubix/models/item.rb
+- lib/rubix/models/user_group.rb
+- lib/rubix/models/operation.rb
+- lib/rubix/models/host.rb
+- lib/rubix/models/host_group.rb
+- lib/rubix/models/model.rb
+- lib/rubix/models/medium.rb
+- lib/rubix/models/time_series.rb
+- lib/rubix/models/condition.rb
+- lib/rubix/models/application.rb
+- lib/rubix/models/user.rb
+- lib/rubix/examples/simple_zabbix_monitor.rb
+- lib/rubix/examples/simple_uptime_monitor.rb
+- lib/rubix/examples/simple_cluster_monitor.rb
+- lib/rubix/examples/simple_chef_monitor.rb
+- lib/rubix/auto_sender.rb
+- lib/rubix/sender.rb
+- lib/rubix/log.rb
+- lib/rubix/models.rb
+- lib/rubix/monitors.rb
+- lib/rubix/response.rb
+- lib/rubix/associations/has_many_hosts.rb
+- lib/rubix/associations/has_many_applications.rb
 - lib/rubix/associations/belongs_to_media_type.rb
 - lib/rubix/associations/belongs_to_template.rb
+- lib/rubix/associations/has_many_host_groups.rb
+- lib/rubix/associations/has_many_users.rb
+- lib/rubix/associations/has_many_conditions.rb
 - lib/rubix/associations/belongs_to_user.rb
 - lib/rubix/associations/belongs_to_user_group.rb
-- lib/rubix/associations/has_many_applications.rb
-- lib/rubix/associations/has_many_conditions.rb
-- lib/rubix/associations/has_many_host_groups.rb
-- lib/rubix/associations/has_many_hosts.rb
+- lib/rubix/associations/belongs_to_host.rb
+- lib/rubix/associations/belongs_to_item.rb
 - lib/rubix/associations/has_many_items.rb
 - lib/rubix/associations/has_many_templates.rb
+- lib/rubix/associations/belongs_to_action.rb
 - lib/rubix/associations/has_many_user_groups.rb
 - lib/rubix/associations/has_many_user_macros.rb
-- lib/rubix/associations/has_many_users.rb
-- lib/rubix/associations.rb
-- lib/rubix/auto_sender.rb
-- lib/rubix/connection.rb
-- lib/rubix/examples/simple_chef_monitor.rb
-- lib/rubix/examples/simple_cluster_monitor.rb
-- lib/rubix/examples/simple_uptime_monitor.rb
-- lib/rubix/examples/simple_zabbix_monitor.rb
-- lib/rubix/log.rb
-- lib/rubix/models/action.rb
-- lib/rubix/models/application.rb
-- lib/rubix/models/condition.rb
-- lib/rubix/models/host.rb
-- lib/rubix/models/host_group.rb
-- lib/rubix/models/item.rb
-- lib/rubix/models/media_type.rb
-- lib/rubix/models/medium.rb
-- lib/rubix/models/model.rb
-- lib/rubix/models/operation.rb
-- lib/rubix/models/script.rb
-- lib/rubix/models/template.rb
-- lib/rubix/models/time_series.rb
-- lib/rubix/models/trigger.rb
-- lib/rubix/models/user.rb
-- lib/rubix/models/user_group.rb
-- lib/rubix/models/user_macro.rb
-- lib/rubix/models.rb
 - lib/rubix/monitors/chef_monitor.rb
 - lib/rubix/monitors/cluster_monitor.rb
-- lib/rubix/monitors/monitor.rb
 - lib/rubix/monitors/zabbix_monitor.rb
-- lib/rubix/monitors.rb
-- lib/rubix/response.rb
-- lib/rubix/sender.rb
-- lib/rubix.rb
-- spec/data/test_template.xml
-- spec/requests/action_request_spec.rb
-- spec/requests/application_request_spec.rb
-- spec/requests/connection_request_spec.rb
-- spec/requests/host_group_request_spec.rb
-- spec/requests/host_request_spec.rb
-- spec/requests/item_request_spec.rb
-- spec/requests/media_type_request_spec.rb
-- spec/requests/script_request_spec.rb
-- spec/requests/template_request_spec.rb
-- spec/requests/time_series_request_spec.rb
-- spec/requests/trigger_request_spec.rb
-- spec/requests/user_group_request_spec.rb
-- spec/requests/user_macro_request_spec.rb
-- spec/requests/user_request_spec.rb
-- spec/rubix/auto_sender_spec.rb
-- spec/rubix/connection_spec.rb
+- lib/rubix/monitors/monitor.rb
+- lib/rubix/connection.rb
+- lib/rubix/associations.rb
+- spec/test.yml
 - spec/rubix/model_spec.rb
-- spec/rubix/monitors/chef_monitor_spec.rb
-- spec/rubix/monitors/cluster_monitor_spec.rb
+- spec/rubix/auto_sender_spec.rb
 - spec/rubix/monitors/monitor_spec.rb
+- spec/rubix/monitors/chef_monitor_spec.rb
 - spec/rubix/monitors/zabbix_monitor_spec.rb
+- spec/rubix/monitors/cluster_monitor_spec.rb
 - spec/rubix/response_spec.rb
 - spec/rubix/sender_spec.rb
+- spec/rubix/connection_spec.rb
+- spec/requests/time_series_request_spec.rb
+- spec/requests/media_type_request_spec.rb
+- spec/requests/script_request_spec.rb
+- spec/requests/item_request_spec.rb
+- spec/requests/action_request_spec.rb
+- spec/requests/host_group_request_spec.rb
+- spec/requests/user_macro_request_spec.rb
+- spec/requests/connection_request_spec.rb
+- spec/requests/template_request_spec.rb
+- spec/requests/trigger_request_spec.rb
+- spec/requests/host_request_spec.rb
+- spec/requests/user_request_spec.rb
+- spec/requests/user_group_request_spec.rb
+- spec/requests/application_request_spec.rb
 - spec/spec_helper.rb
-- spec/support/configliere_helper.rb
 - spec/support/integration_helper.rb
 - spec/support/response_helper.rb
-- spec/test.yml
+- spec/support/configliere_helper.rb
+- spec/data/test_template.xml
 - LICENSE
 - README.rdoc
 - VERSION
 homepage: http://github.com/dhruvbansal/rubix
 licenses: []
-
 post_install_message: 
 rdoc_options: []
-
-require_paths: 
+require_paths:
 - lib
-required_ruby_version: !ruby/object:Gem::Requirement 
+required_ruby_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-
 rubyforge_project: 
-rubygems_version: 1.8.15
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: A Ruby client for configuring and writing data to Zabbix
 test_files: []
-
 has_rdoc: