A minimal monitoring system
Go to file
2018-04-09 12:08:42 -07:00
minitor Run pre-commit to clean files 2018-04-09 12:08:42 -07:00
tests Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
.gitignore Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
.pre-commit-config.yaml Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
LICENSE Run pre-commit to clean files 2018-04-09 12:08:42 -07:00
Makefile Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
README.md Run pre-commit to clean files 2018-04-09 12:08:42 -07:00
requirements-dev.txt Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
requirements.txt Add back requirements.txt to install from setup 2018-02-16 09:55:10 -08:00
sample-config.yml Add exponential backoff 2018-02-17 20:45:37 -08:00
setup.cfg Prepare for pypi 2018-02-16 17:49:33 -08:00
setup.py Run pre-commit to clean files 2018-04-09 12:08:42 -07:00
tox.ini Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00

minitor

A minimal monitoring system

What does it do?

Minitor accepts a YAML configuration file with a set of commands to run and a set of alerts to execute when those commands fail. It is designed to be as simple as possible and relies on other command line tools to do checks and issue alerts.

But why?

I'm running a few small services and found Sensu, Consul, Nagios, etc. to all be far too complicated for my usecase.

So how do I use it?

Running

Install and execute with:

pip install minitor
minitor

If locally developing you can use:

make run

It will read the contents of config.yml and begin its loop. You could also run it directly and provide a new config file via the --config argument.

Configuring

In this repo, you can explore the sample-config.yml file for an example, but the general structure is as follows. It should be noted that environment variable interpolation happens on load of the YAML file. Also, when alerts are executed, they will be passed through Python's format function with arguments for some attributes of the Monitor. Currently this is limited to {monitor_name}.