A small monitoring system to check nodes and create notifications.
Go to file
Gibheer dece1ac2dc add level mappings
This allows to map the command exit codes to any other output level
which can then be reported by the notification plugin.
With the provided colors, the frontend will show them accordingly.
2018-12-11 12:37:30 +01:00
cmd add level mappings 2018-12-11 12:37:30 +01:00
schema add level mappings 2018-12-11 12:37:30 +01:00
.gitignore ignore live config files 2018-11-19 14:17:11 +01:00
go.mod initial commit 2018-11-16 10:39:21 +01:00
go.sum initial commit 2018-11-16 10:39:21 +01:00
moncheck.conf.example moncheck - add timeout to example config 2018-11-29 10:46:38 +01:00
monwork.conf.example add example config files 2018-11-19 14:15:31 +01:00
README.md initial commit 2018-11-16 10:39:21 +01:00

monzero

Monzero is a collection of tools with the purpose of running monitoring checks and triggering notifications.

requirements

runtime requirements:

  • PostgreSQL >= 10.0

build requirements:

  • Go >= 1.11

components

The following components exist:

moncheck

Moncheck is the daemon that runs the checks and generates notifications in the database. It is possible to run multiple instances of moncheck, as it uses PostgreSQL as a coordinator through the PostgreSQL internal locking mechanism.

Moncheck uses the table active_checks to detect which checks to run.

monfront

Monfront is a webfrontend to view the current state of all checks, configure hosts, groups, checks and view current notifications. It is possible to run multiple instances.

monwork

Monwork is a small server that does all the maintenance work in the background. It is responsible to cleanup the history and generate the configuration.

The configuration is generated into active_checks when an entry in nodes, command or checks was changed (detected through the updated column).