Flapjack is highly scalable and distributed monitoring system.
It understands the Nagios plugin format, and can easily be scaled from 1 server to 1000.
These install instructions are probably wrong. Follow them best you can, and please report bugs as you find them!
Add the following lines to /etc/apt/sources.list
deb http://ppa.launchpad.net/ubuntu-ruby-backports/ubuntu hardy main
deb http://ppa.launchpad.net/auxesis/ppa/ubuntu hardy main
Add GPG keys for the repos:
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 288BA53BCB7DA731
Update your package list:
sudo apt-get update
Install Ruby dependencies:
sudo apt-get install build-essential libsqlite3-dev
Install rubygems + beanstalkd:
sudo apt-get install rubygems beanstalkd
Set ENABLED=1
in /etc/default/beanstalkd
.
Start beanstalkd:
sudo /etc/init.d/beanstalkd start
Install the following software through your package manager or from source:
- beanstalkd (from http://xph.us/software/beanstalkd/)
- libevent (from http://monkey.org/~provos/libevent/)
Add the Gemcutter RubyGems server to your Gem sources:
sudo gem sources -a http://gemcutter.org
Install the Flapjack gem:
sudo gem install flapjack
Then run the magic configuration script to set up init scripts:
sudo install-flapjack-systemwide
The script will prompt you if it wants to do anything destructive.
Make sure beanstalkd is running.
You'll want to set up /etc/flapjack/recipients.conf
so notifications can be sent via
flapjack-notifier
:
[John Doe]
email = [email protected]
jid = [email protected]
phone = +61 400 111 222
pager = 61400111222
[Jane Doe]
email = [email protected]
jid = [email protected]
phone = +61 222 333 111
pager = 61222333111
You also need to set up /etc/flapjack/notifier.conf
:
# top level
[notifier]
notifier-directories = /usr/lib/flapjack/notifiers/ /path/to/my/notifiers
notifiers = mailer, xmpp
# persistence layers
[persistence]
backend = data_mapper
uri = sqlite3:///tmp/flapjack.db
# message transports
[transport]
backend = beanstalkd
host = localhost
port = 11300
# notifiers
[mailer-notifier]
from_address = [email protected]
[xmpp-notifier]
jid = [email protected]
password = barfoo
# filters
[filters]
chain = ok, downtime, any_parents_failed
Start up a cluster of workers:
flapjack-worker-manager start
This will spin up 5 workers in the background. You can specify how many workers to start:
flapjack-worker-manager start --workers=10
Each of the flapjack-worker
s will output to syslog (check in /var/log/messages).
Start up the notifier:
flapjack-notifier-manager start --recipients /etc/flapjack/recipients.conf
Currently there are email and XMPP notifiers.
You'll want to get a copy of (http://github.com/auxesis/flapjack-admin/)[flapjack-admin] to set up some checks, then run its populator to get them into Flapjack.
flapjack-worker
=> executes checks, reports resultsflapjack-worker-manager
=> starts/stops a cluster offlapjack-worker
flapjack-notifier
=> gets results, notifies people if necessaryflapjack-stats
=> gets stats from beanstalkd tubes (useful for benchmarks + performance analysis)flapjack-benchmark
=> benchmarks various persistence/transport backend combinations
You can use the provided init scripts to start Flapjack on boot.
To start:
/etc/init.d/flapjack-workers start
/etc/init.d/flapjack-notifier start
To set Flapjack to start on boot (Ubuntu):
sudo update-rc.d flapjack-workers defaults
sudo update-rc.d flapjack-notifier defaults
Config for the init scripts can be found in /etc/defaults
.
Tests are in spec/
and features/
.
To run tests:
$ rake spec
$ rake cucumber
------------------- -------------------
| web interface / | | visualisation / |
| dsl / flat file | | reporting |
------------------- -------------------
| |
\ /
\ /
---------------
| persistence |
---------------
|
-------------------------------
| |
| |
| |
------------- ------------
| populator |--- -----| notifier |
------------- | | ------------
| |
--------------
| beanstalkd |
--------------
|
-----------------------------------
| | |
---------- ---------- ----------
| worker | | worker | | worker |
---------- ---------- ----------
- populator determines checks that need to occur, and puts checks onto
jobs
tube- populator fetches jobs from a database
- populator can be swapped out to get checks from a dsl or flat files
- workers pop a check off the beanstalk, perform check, put result onto
results
tube, re-add check tojobs
tube with a delay. - notifier pops results off
results
tube, notifies as necessary
- bump version number + release date in gemspec
- create a new tag with
git tag -a -m "releasing 0.9" 0.9
- push to github with
git push --tags
- create a new gem with
rake build
- push gem to Gemcutter with
rake push