A minimal monitoring system
Go to file
Ian Fijolek 8169b4257a
All checks were successful
continuous-integration/drone/push Build is passing
Fix drone and travis builds
* Correct env variable name in minitor_test
* Adding more test environments, skipping python 3.5
because lack of assert_called_once support
* Using default travis python environments
2019-06-03 10:56:42 -07:00
examples Add docker check example 2019-05-31 16:43:14 -07:00
minitor Fix metrics exporting 2018-10-29 11:58:14 -07:00
scripts Add new scripts for checking status of Docker services 2019-05-31 16:43:14 -07:00
tests Fix drone and travis builds 2019-06-03 10:56:42 -07:00
.dockerignore Add example exporting metrics to Prometheus 2019-05-31 16:43:14 -07:00
.drone.yml Fix drone and travis builds 2019-06-03 10:56:42 -07:00
.gitignore Add tox, pre-commit and dummy test. 2018-04-09 10:44:30 -07:00
.pre-commit-config.yaml Fix drone and travis builds 2019-06-03 10:56:42 -07:00
.travis.yml Fix drone and travis builds 2019-06-03 10:56:42 -07:00
Dockerfile Add new scripts for checking status of Docker services 2019-05-31 16:43:14 -07:00
LICENSE Run pre-commit to clean files 2018-04-09 12:08:42 -07:00
Makefile Add new Prometheus metrics endpoint 2018-07-15 19:12:04 -07:00
README.md Add new Prometheus metrics endpoint 2018-07-15 19:12:04 -07:00
requirements-dev.txt Improve logging such that a test can be written for an alert 2018-04-10 11:06:42 -07:00
requirements.txt Add back requirements.txt to install from setup 2018-02-16 09:55:10 -08:00
sample-config.yml Simplify sample config to work around bug in yamlenv 2019-03-10 16:19:26 -07:00
setup.cfg Prepare for pypi 2018-02-16 17:49:33 -08:00
setup.py Add example exporting metrics to Prometheus 2019-05-31 16:43:14 -07:00
tox.ini Add the ability to include last command output in the alert 2018-04-18 17:16:26 -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.

Docker

You can pull this repository directly from Docker:

docker pull iamthefij/minitor

The Docker image uses a default config.yml that is copied from sample-config.yml. This won't really do anything for you, so when you run the Docker image, you should supply your own config.yml file:

docker run -v $PWD/config.yml:/app/config.yml iamthefij/minitor

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. The following monitor specific variables can be referenced using Python formatting syntax:

token value
{alert_count} Number of times this monitor has alerted
{alert_message} The exception message that was raised
{failure_count} The total number of sequential failed checks for this monitor
{last_output} The last returned value from the check command to either stderr or stdout
{last_success} The ISO datetime of the last successful check
{monitor_name} The name of the monitor that failed and triggered the alert

Metrics

As of v0.3.0, Minitor supports exporting metrics for Prometheus. Prometheus is an open source tool for reading and querying metrics from different sources. Combined with another tool, Grafana, it allows building of charts and dashboards. You could also opt to just use Minitor to log check results, and instead do your alerting with Grafana.

It is also possible to use the metrics endpoint for monitoring Minitor itself! This allows setting up multiple instances of Minitor on different servers and have them monitor each-other so that you can detect a minitor outage.

To run minitor with metrics, use the --metrics (or -m) flag. The metrics will be served on port 8080 by default, though it can be overriden using --metrics-port (or -p)

minitor --metrics
# or
minitor --metrics --metrics-port 3000

Contributing

Whether you're looking to submit a patch or just tell me I broke something, you can contribute through the Github mirror and I can merge PRs back to the source repository.

Primary Repo: https://git.iamthefij.com/iamthefij/minitor.git

Github Mirror: https://github.com/IamTheFij/minitor.git