rabbithutch 0.1.4 → 0.1.5

data/.gitignore

@@ -1,24 +1,24 @@
-*~
-*.gem
-*.rbc
-.bundle
-.config
-coverage
-InstalledFiles
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-
-# YARD artifacts
-.yardoc
-_yardoc
-doc/
-
-.project
-*.pid
-
-
+*~
+*.gem
+*.rbc
+.bundle
+.config
+coverage
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+# YARD artifacts
+.yardoc
+_yardoc
+doc/
+
+.project
+*.pid
+
+

data/Gemfile

@@ -1,4 +1,4 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in hash-that-tree.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in hash-that-tree.gemspec
+gemspec

data/Gemfile.lock

@@ -1,55 +1,68 @@
-PATH
-  remote: .
-  specs:
-    rabbithutch (0.1.3)
-      amqp
-      bson_ext
-      daemons
-      eventmachine
-      log4r
-      logger
-      mongo
-      mongo_ext
-      mq
-      mustache
-      thor
-      yard
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    activesupport (3.2.9)
-      i18n (~> 0.6)
-      multi_json (~> 1.0)
-    amq-client (0.9.10)
-      amq-protocol (>= 0.9.4)
-      eventmachine
-    amq-protocol (1.0.1)
-    amqp (0.9.8)
-      amq-client (~> 0.9.5)
-      amq-protocol (>= 0.9.4)
-      eventmachine
-    bson (1.8.0)
-      activesupport
-    bson_ext (1.8.0)
-      bson (~> 1.8.0)
-    daemons (1.1.9)
-    eventmachine (1.0.0)
-    i18n (0.6.1)
-    log4r (1.1.10)
-    logger (1.2.8)
-    mongo (1.8.0)
-      bson (~> 1.8.0)
-    mongo_ext (0.19.3)
-    mq (0.1.3)
-    multi_json (1.5.0)
-    mustache (0.99.4)
-    thor (0.16.0)
-    yard (0.8.3)
-
-PLATFORMS
-  ruby
-  x86-mingw32
-
-DEPENDENCIES
-  rabbithutch!
+PATH
+  remote: .
+  specs:
+    rabbithutch (0.1.4)
+      amqp
+      bson_ext
+      daemons
+      eventmachine
+      haml
+      log4r
+      logger
+      mongo
+      mongo_ext
+      mq
+      mustache
+      shotgun
+      sinatra
+      thin
+      thor
+      yard
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    amq-client (0.9.10)
+      amq-protocol (>= 0.9.4)
+      eventmachine
+    amq-protocol (1.0.1)
+    amqp (0.9.8)
+      amq-client (~> 0.9.5)
+      amq-protocol (>= 0.9.4)
+      eventmachine
+    bson (1.8.2)
+    bson_ext (1.8.1)
+      bson (~> 1.8.1)
+    daemons (1.1.9)
+    eventmachine (1.0.0)
+    haml (3.1.7)
+    log4r (1.1.10)
+    logger (1.2.8)
+    mongo (1.8.1)
+      bson (~> 1.8.1)
+    mongo_ext (0.19.3)
+    mq (0.1.3)
+    mustache (0.99.4)
+    rack (1.4.4)
+    rack-protection (1.3.2)
+      rack
+    shotgun (0.9)
+      rack (>= 1.0)
+    sinatra (1.3.3)
+      rack (~> 1.3, >= 1.3.6)
+      rack-protection (~> 1.2)
+      tilt (~> 1.3, >= 1.3.3)
+    thin (1.5.0)
+      daemons (>= 1.0.9)
+      eventmachine (>= 0.12.6)
+      rack (>= 1.0.0)
+    thor (0.16.0)
+    tilt (1.3.3)
+    yard (0.8.3)
+
+PLATFORMS
+  ruby
+  x86-mingw32
+
+DEPENDENCIES
+  rabbithutch!

data/LICENSE.txt

@@ -1,22 +1,22 @@
-Copyright (c) 2012 John Ryan
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+Copyright (c) 2012 John Ryan
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,107 +1,137 @@
-#rabbit-hutch
-
-RabbitMq Trace Logger - Listen to multiple RabbitMq instances and log them to a 
-single location or MongoDb database. 
-
-# Overview
-	
-A ruby service for monotoring the trace output on RabbitMq Nodes and writing the 
-output to console, Log files or MongoDb.
-
-Once tracing is started on the target rabbitMQ nodes, the service creates a queue 
-"rabbithutch" that binds to the exchange "amq.rabbitmq.trace". All messages that arrive
-on the queue are then picked up by any registered consumers and written to standard 
-output, a log file or a MongoDb Database.
-	
-# Environment
-	
-	* Linux
-	* Windows
-	
-# Installation
-	
-	##Activate tracing on rabbitmq server
-	
-	run the following command on each server you want to trace
-	rabbitmqctl trace_on
-	
-	##Install the rabbit-hutch service
-	
-	gem install rabbithutch
-
-# Usage
-
-	Run as a command line process with a config file
-	rabbithutch run -- ~/config.yaml
-	
-	Run as a service
-	rabbithutch start -- ~/config.yaml
-	
-	For help on the service
-	rabbithutch
-	
-# Configuration
-
-	To add RabbitMq nodes to monitor and consumers to enable you will need to change the configuration.
-	
-	The config below shows two RabbitMq nodes with each with console, mongoDb and log file consumers
-	
-	./config.yaml
-	
-	application:
-    exchangename: amq.rabbitmq.trace
-    queuename: rabbithutch
-    
-	rabbitmq:
-		hosts:
-		  - displayname: local1
-			enabled: true
-			hostname: 127.0.0.1
-			username: guest
-			password: guest
-		  - displayname: local2
-			enabled: false
-			hostname: 127.2.2.2
-			username: guest
-			password: guest
-
-	consumers_config:
-		consumers:
-		  - name: console_consumer
-			enabled: true
-		  - name: mongo_consumer
-			enabled: true
-			hostname: 127.0.0.1
-			username: guest
-			password: guest
-			database_prefix: rhutch_
-			port: 27017
-		  - name: log4r_consumer
-			enabled: true
-			log_location: /tmp
-			log_prefix: rhutch_
-	
-#Contributing
-	
-	Fork it
-	Create your feature branch (git checkout -b my-new-feature)
-	Commit your changes (git commit -am 'Add some feature')
-	Push to the branch (git push origin my-new-feature)
-	Create new Pull Request
-
-## Create the gem
-	
-	Build and Test Locally
-	-gem build rabbithutch.gemspec
-	-gem install rabbithutch-X.X.X # where X.X.X is the version of the compiled gemspec
-	
-	Build and deploy to rubygems.org
-	-gem update --system
-	-gem build rabbithutch.gemspec
-	-gem push rabbithutch-0.0.1.gem # where X.X.X is the version of the compiled gemspec
-
-#To do
-
-	- [ ] Add Http Appender to post messages to url e.g. pastebin.org or mongodb REST interface
-	- [ ] Come up with better config mgt for gems like adding a management Command Line Interface to set env settings
-
+#rabbit-hutch
+
+RabbitMq Trace Logger - Listen to multiple RabbitMq instances and log them to a 
+single location or MongoDb database. 
+
+Applications included
+* rabbithutch - a service to listen to the exchanges
+* rabbithutchweb - a web site to configure the service 
+
+# Overview
+	
+A ruby service for monotoring the trace output on RabbitMq Nodes and writing the 
+output to console, Log files or MongoDb.
+
+Once tracing is started on the target rabbitMQ nodes, the service creates a queue 
+"rabbithutch" that binds to the exchange "amq.rabbitmq.trace". All messages that arrive
+on the queue are then picked up by any registered consumers and written to standard 
+output, a log file or a MongoDb Database.
+	
+# Environment
+
+	This has been tested on 
+	* Ubuntu Linux
+	* Windows 8
+	
+# Installation
+	
+	##Activate tracing on rabbitmq server
+	
+	run the following command on each server you want to trace
+	rabbitmqctl trace_on
+	
+	##Install the rabbit-hutch service
+	
+	gem install rabbithutch
+
+#RabbitMq Configuration
+
+	In order for tracing to work, the trace_on option must be enabled on all rabbitMq nodes.
+	Turn on tracing on the nodes using the following command:
+	rabbitmqctl trace_on
+	
+# Usage
+	
+	Start up the Web Interface
+		
+		rabbithutchweb
+
+	Run as a command line process with a config file
+	
+		rabbithutch run -- ~/config.yaml
+	
+	Run as a service
+		
+		rabbithutch start -- ~/config.yaml
+	
+	For help on the service
+		
+		rabbithutch
+
+# Troubleshooting
+	
+	Web Manager 
+	If the web service has not been shut down properly the process my still be alive in the background 
+	ERROR:
+		 (/home/USERNAME/.rvm/gems/ruby-1.9.3-p327/gems/eventmachine-1.0.0/lib/eventmachine.rb:526:in 
+		`start_tcp_server': no acceptor (port is in use or requires root privileges) (RuntimeError))
+	To fix this kill the process named shotgun
+	- ps aux | grep shot
+	- kill -9 (the process number)
+
+# Configuration
+
+	To add RabbitMq nodes to monitor and consumers to enable you will need to change the configuration.
+	
+	The config below shows two RabbitMq nodes with each with console, mongoDb and log file consumers
+	
+	./config.yaml
+	
+	application:
+    exchangename: amq.rabbitmq.trace
+    queuename: rabbithutch
+    
+	rabbitmq:
+		hosts:
+		  - displayname: local1
+			enabled: true
+			hostname: 127.0.0.1
+			username: guest
+			password: guest
+		  - displayname: local2
+			enabled: false
+			hostname: 127.2.2.2
+			username: guest
+			password: guest
+
+	consumers_config:
+		consumers:
+		  - name: console_consumer
+			enabled: true
+		  - name: mongo_consumer
+			enabled: true
+			hostname: 127.0.0.1
+			username: guest
+			password: guest
+			database_prefix: rhutch_
+			port: 27017
+		  - name: log4r_consumer
+			enabled: true
+			log_location: /tmp
+			log_prefix: rhutch_
+	
+#Contributing
+	
+	Fork it
+	Create your feature branch (git checkout -b my-new-feature)
+	Commit your changes (git commit -am 'Add some feature')
+	Push to the branch (git push origin my-new-feature)
+	Create new Pull Request
+
+## Create the gem
+	
+	Build and Test Locally
+	-gem build rabbithutch.gemspec
+	-gem install rabbithutch-X.X.X # where X.X.X is the version of the compiled gemspec
+	
+	Build and deploy to rubygems.org
+	-gem update --system
+	-gem build rabbithutch.gemspec
+	-gem push rabbithutch-0.0.1.gem # where X.X.X is the version of the compiled gemspec
+
+#To do
+
+	- [ ] Add Http Appender to post messages to url e.g. pastebin.org or mongodb REST interface
+	- [ ] Come up with better config mgt for gems like adding a management Command Line Interface to set env settings
+	- [x] Add a Web UI to manage the service 
+