chef-monitor 0.1.5 → 0.1.6

data/README.md

@@ -0,0 +1,121 @@
+#CHEF-MONITOR
+
+Chef monitor has two executables:
+  - chef-logmon         (this will be activated on all frontend servers)
+  - chef-worker         (this will be activated on your monitor/backend server)
+
+#CHEF HA
+
+When you have Chef in HA mode, your environment will look something like this:
+
+    HA Setup
+
+     public zone   |        dmz zone        |       db zone
+    ---------------|------------------------|-----------------------
+                   |                        |
+                   |    frontend-server     |               backend-server
+                   |    webserver01         |          /    dbserver01
+                   |    10.1.1.10/24        |         /     10.1.5.110/24
+                   |                        |        /
+      internet     |                        |  vip  <
+                   |                        |   ^    \
+                   |    frontend-server     |   |     \     backend-server
+                   |    webserver02         |   |      \    dbserver02
+                   |    10.1.1.20/24        |   |           10.1.5.120/24
+                                                |
+                                                             ----------------
+                                            10.1.5.90/24    | monitor-server |
+                                            keepalived      | monserver01    |
+                                                            | 10.1.5.130/24  |
+                                                             ----------------
+
+When running this environment, I suggest you configure the new monitor server.  
+The Back-end server and monitor server can also be only one single server.  
+If you don't have HA mode, then the environment will look something like this:  
+
+    Single Setup
+    
+     public zone   |    cloud server        |
+    ---------------|------------------------|
+                   |                        |
+                   |    chefserver          |
+      internet     |    chefserver01        |
+                   |    10.1.1.10/24        |
+                   |                        |
+  
+  
+#CHEF-LOGMON:
+
+The logmon tool will run on every frontend server within your HA environment or on the  
+chefserver in a more basic environment and is responsible for the following tasks:  
+  
+  - Tail your NGINX log and record all POST/PUTS/DELETES  
+  - This information is sent to your Rabbit-MQ server (which comes default with chef)  
+  
+Basically every change that's being made to chef is registered within RabbitMQ.  
+  
+#CHEF-WORKER:
+
+The worker tool will run on your monitor server within the HA environment or on the
+chefserver in a more basic environment and is responsible for the following tasks:
+
+  - Get the messages from RabbitMQ
+  - Download the objects from chef that are changed
+  - Commit the changes within a GIT repository
+
+In this way every modified object is registered with a GIT commit and a POST-COMMIT script  
+will email the differences to any configured email address. This POST-COMMIT part is not  
+within the GEM, but comes with the chef-monitor chef cookbook.  
+  
+#CONFIGURATION:
+
+In order to execute both tools, you will need the following configuration settings:
+
+    chef_url       "https://10.1.5.90"
+    node_name      "monitor"
+    client_key     "/opt/chef-monitor/monitor.pem"
+    mq_server      "10.1.5.90"
+    mq_queue       "monitor_tasks"
+    download_path  "/opt/chef-monitor/orgs"
+    log_dir        "/var/log/chef-monitor"
+    pid_dir        "/var/run/chef-monitor"
+    mon_file       "/var/log/opscode/nginx/access.log"
+
+Save these settings into /opt/chef-monitor/config.rb (the cookbook will do this for you)  
+Make sure your monitor user is created on your chef server and has enough rights to download  
+all objects within your organization that you want to monitor.  
+  
+Create a directory within your [download_path] with the same name as your organization.  
+Initialize this directory with the following commands:  
+
+    git init  
+    touch dummy  
+    git add .
+    git commit -am "enable git control"
+
+Add some git configuration settings for the POST-COMMIT script and chef-monitor tools.  
+
+    git config hooks.mailinglist sander.botman@gmail.com
+    git config hooks.emailprefix <YOUR_ORGANIZATION>
+    git config hooks.emaildomain @your.domain.com
+
+Set the project name within the gitrepo, so you can identify your chef environment.  
+
+    echo MYCHEF > ./.git/description
+
+
+#EXECUTION:
+  
+After these settings, you should be able to run the tools:  
+On all your frontend servers:  
+
+    chef-logmon run -- -C /opt/chef-monitor/config.rb     #<run interactive>
+    chef-logmon start -- -C /opt/chef-monitor/config.rb   #<run as service>
+    chef-logmon stop                                      #<stop service>
+
+On your monitor server:
+
+    chef-worker run -- -C /opt/chef-monitor/config.rb             #<run interactive>
+    chef-worker start -- -C /opt/chef-monitor/config.rb           #<run as service>
+    chef-worker stop                                              #<stop service>
+    chef-worker run -- -C /opt/chef-monitor/config.rb -O my_org  #<populates the repo: my_org for the first time>

data/bin/chef-logmon

@@ -15,6 +15,7 @@
 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 # See the License for the specific language governing permissions and
 # limitations under the License.
+#
 
 require "chef_logmon"
 require 'rubygems'

data/bin/chef-worker

@@ -1,5 +1,4 @@
 #!/usr/bin/env ruby
-#!/opt/chef/embedded/bin/ruby
 #
 # Author:: Sander Botman (<sander.botman@gmail.com>)
 # Copyright:: Copyright (c) 2014 Sander Botman.
@@ -16,7 +15,8 @@
 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 # See the License for the specific language governing permissions and
 # limitations under the License.
-# $:.unshift(File.join(File.dirname(__FILE__), "..", "lib"))
+#
+
 require "chef_worker"
 require 'rubygems'
 require 'bunny'

data/chef-monitor.gemspec

@@ -10,7 +10,7 @@ Gem::Specification.new do |s|
   s.extra_rdoc_files  = ["LICENSE"]
   s.authors           = ["Sander Botman"]
   s.email             = ["sander.botman@gmail.com"]
-  s.homepage          = "https://github.com/schubergphilis/chef-monitor"
+  s.homepage          = "https://github.com/schubergphilis/chef-monitor-gem"
   s.summary           = %q{Chef Monitoring tool to monitor all changes made}
   s.description       = s.summary
   s.files             = `git ls-files`.split("\n")

data/lib/chef_monitor/logmon.rb

@@ -32,7 +32,8 @@ class Monitor
           mon.backward(1)
           mon.tail { |line|
             data = scan(line)
-            unless data.nil? || data['org'].nil?
+            # skipping the objects 'checksum-.*' and 'reports'
+            unless data.nil? || data['org'].nil? || data['object'] =~  /(^checksum-.*$|^reports$)/
               Monitor::Log.new(data, "INFO")
               q.publish(data, :persistent => true, :content_type => "application/json")
             end

data/lib/chef_monitor/version.rb

@@ -16,6 +16,6 @@
 # limitations under the License.
 
 class Monitor
-  VERSION = "0.1.5"
+  VERSION = "0.1.6"
   MAJOR, MINOR, TINY = VERSION.split('.')
 end

data/lib/chef_monitor/worker.rb

@@ -15,7 +15,6 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-
 class Monitor
   class Worker
     def run

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: chef-monitor
 version: !ruby/object:Gem::Version
-  version: 0.1.5
+  version: 0.1.6
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-11 00:00:00.000000000 Z
+date: 2014-04-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bunny
@@ -69,9 +69,8 @@ extensions: []
 extra_rdoc_files:
 - LICENSE
 files:
-- .gitignore
 - LICENSE
-- README
+- README.md
 - Rakefile
 - bin/chef-logmon
 - bin/chef-worker
@@ -85,7 +84,7 @@ files:
 - lib/chef_monitor/version.rb
 - lib/chef_monitor/worker.rb
 - lib/chef_worker.rb
-homepage: https://github.com/schubergphilis/chef-monitor
+homepage: https://github.com/schubergphilis/chef-monitor-gem
 licenses:
 - Apache 2.0
 post_install_message: 
@@ -106,7 +105,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
 summary: Chef Monitoring tool to monitor all changes made

data/.gitignore

@@ -1,4 +0,0 @@
-/bin/test*
-/pkg
-/config
-/orgs

data/README

@@ -1,131 +0,0 @@
-#
-# Author:: Sander Botman (<sander.botman@gmail.com>)
-# Copyright:: Copyright (c) 2014 Sander Botman.
-# License:: Apache License, Version 2.0
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-CHEF-MONITOR
-
-Chef monitor has two executables:
-  - chef-logmon		(this will be activated on all frontend servers)
-  - chef-worker		(this will be activated on your monitor/backend server)
-
-
-Chef HA configuration:
-
-When you have Chef in HA mode, your environment will look something like this:
-
- public zone   |        dmz zone        |       db zone
----------------|------------------------|-----------------------
-               |                        |
-               |    frontend-server     |               backend-server
-               |    webserver01         |          /    dbserver01
-               |    10.1.1.10/24        |         /     10.1.5.110/24
-               |                        |        /
-  internet     |                        |  vip  <
-               |                        |   ^    \
-               |    frontend-server     |   |     \     backend-server
-               |    webserver02         |   |      \    dbserver02
-               |    10.1.1.20/24        |   |           10.1.5.120/24
-                                            |
-                                                         ----------------
-                                        10.1.5.90/24    | monitor-server |
-                                        keepalived      | monserver01    |
-                                                        | 10.1.5.130/24  |
-                                                         ----------------
-          
-When running this environment, I suggest you configure the new monitor server.
-The frondend server and monitor server can also be only one single server.
-If you don't have HA mode, then the environment will look something like this:
-
- public zone   |    cloud server        |
----------------|------------------------|
-               |                        |
-               |    chefserver          |
-  internet     |    chefserver01        |
-               |    10.1.1.10/24        |
-               |                        |
-
-
-CHEF-LOGMON:
-
-The logmon tool will run on every frontend server within your HA environment or on the 
-chefserver in a more basic environment and is responsible for the following tasks:
-
-  - Tail your NGINX log and record all POST/PUTS/DELETES
-  - This information is sent to your Rabbit-MQ server (which comes default with chef)
-
-Basically every change that's being made to chef is registered within RabbitMQ.
-
-
-CHEF-WORKER:
-
-The worker tool will run on your monitor server within the HA environment or on the 
-chefserver in a more basic environment and is responsible for the following tasks:
-
-  - Get the messages from RabbitMQ
-  - Download the objects from chef that are changed
-  - Commit the changes within a GIT repository
-
-In this way every modified object is registered with a GIT commit and a POST-COMMIT script 
-will email the differences to any configured email address. This POST-COMMIT part is not
-within the GEM, but comes with the chef-monitor chef cookbook.
-
-CONFIGURATION:
-
-In order to execute both tools, you will need the following configuration settings:
-
-chef_url       "https://10.1.5.90"
-node_name      "monitor"
-client_key     "/opt/chef-monitor/monitor.pem"
-mq_server      "10.1.5.90"
-mq_queue       "monitor_tasks"
-download_path  "/opt/chef-monitor/orgs"
-log_dir        "/var/log/chef-monitor"
-pid_dir        "/var/run/chef-monitor"
-mon_file       "/var/log/opscode/nginx/access.log"
-
-Save these settings into /opt/chef-monitor/config.rb
-Make sure your monitor user is created on your chef server and has enough rights to download 
-all objects within your organizaton that you want to monitor.
-
-Create an directory within your [download_path] with the same name as your organization.
-Initialize this directory with the following commands:
-  git init
-  touch dummy
-  git add .
-  git commit -am "enable git control"
-
-Add some git configuration settings for the POST-COMMIT script and chef-monitor tools.
-  git config hooks.mailinglist sander.botman@gmail.com
-  git config hooks.emailprefix <YOUR_ORGANIZATION>
-  git config hooks.emaildomain @your.domain.com
-
-Set the project name within the gitrepo, so you can identify your chef environment.
-  echo MYCHEF > ./.git/description
-  
-
-EXECUTION:
-
-After these settings, you should be able to run the tools:
-On all your frontend servers:
-  chef-logmon run -- -C /opt/chef-monitor/config.rb	<run interactive>
-  chef-logmon start -- -C /opt/chef-monitor/config.rb   <run as service>
-  chef-logmon stop                                      <stop service>
-
-On your monitor server:
-  chef-worker run -- -C /opt/chef-monitor/config.rb     <run interactive>
-  chef-worker start -- -C /opt/chef-monitor/config.rb   <run as service>
-  chef-worker stop                                      <stop service>
-