<commit_before>Zmon is a host monitoring system that is extremely easy to deploy and configure.

Notifications are sent via SMTP or via pushover.net (alerts to mobile devices via Google Cloud Messaging).

Configuration
-------------

TODO: create a web UI for generating the config string based on a form.

Example input string (TODO: move to JSON):

    "disk=/&tcp=localhost:22&sa=&st=yves.junqueira%40gmail.com&sf=root%40cetico.org"

This creates a prober that checks if port 22 is reachable and if the root
filesystem has enough space, sending an email in case of problems.

Installation
----------

Zmon should be run as an unprivileged user. It doesn't need to be installed like normal daemons. 

Download the binary version of a recent release for your platform and gunzip it, or build it from source. Copy the binary to the user's $HOME/bin directory and run it from there.

To ensure that zmon runs after boot, create a crontab entry for re-running Zmon. From the shell, type: 

```
$ crontab -e
```

And add a crontab line such as:

    @hourly nohup $HOME/bin/zmon "disk=/&tcp=localhost:22&sa=&st=email\%40example.com&sf=root\%40zmon.org" &

Notes on using it with crontab:
- it doesn't use special privileges
- the % symbols must be escaped by \<commit_msg>README update<commit_after>Zmon is a host monitoring system that is extremely easy to deploy and configure.

Notifications are sent via SMTP or via pushover.net (alerts to mobile devices via Google Cloud Messaging).

Configuration
-------------

Zmon will eventually have its own minimal web interface for changing the configuration. In the meantime you have to write the config file manually into ~/.zmon. It is a URL-like string like the following:

    "disk=/&tcp=localhost:22&tcp=localhost:80&sa=&st=yves.junqueira%40gmail.com&sf=root%40cetico.org"

This creates a prober that checks if ports 22 and 80 are reachable and if the root filesystem has enough space, sending an email to `st` with a sender of `sf` in case of problems.

Example config string:


Installation
----------

Zmon should be run as an unprivileged user. It doesn't need to be installed like normal daemons. 

Download the binary version of a recent release for your platform and gunzip it, or build it from source. Copy the binary to the user's $HOME/bin directory and run it from there.

To ensure that zmon runs after boot, create a crontab entry for re-running Zmon. From the shell, type: 

```
$ crontab -e
```

And add a crontab line such as:

    @hourly nohup $HOME/bin/zmon "disk=/&tcp=localhost:22&tcp=localhost:80&sa=&st=email\%40example.com&sf=root\%40zmon.org" &

Notes on using it with crontab:
- it doesn't use special privileges
- the % symbols must be escaped by \
{'fraction_non_alphanumeric': 0.08513761467889908, 'fraction_numerical': 0.012477064220183486, 'mean_word_length': 3.9384057971014492, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3885970', 'n_tokens_mistral': 831, 'n_tokens_neox': 777, 'n_words': 380}