bigbrother

Server overseer.

bigbrother runs predefined checks (e.g. HTTP, TCP) every n seconds and notifies (via e.g. Telegram) you if any of these checks fail.

See config.yml.sample for some example checks.

Screenshots

Checks

Currently, the following checks are implemented:

• http - Check a URL for specific for its HTTP status code or content.
• host_ip - Check a host and ip via TCP.
• ftp - Check an FTP or FTPS server: greeting, AUTH TLS, certificate expiry and login.

FTP / FTPS

The ftp check speaks enough of RFC 959 (and RFC 4217 for FTPS) to tell a healthy server from a broken one, which a plain host_ip check on port 21 cannot: it reads the greeting, optionally upgrades to TLS, optionally logs in, then hangs up. It never opens a data connection, so the passive port range does not have to be reachable.

- type: "ftp"
  host: ftp.example.com
  # port: 21
  # tls: "explicit"  # "explicit" | "implicit" | "none"
  # user: "alice"
  # password: "s3cret"
  # match_banner: "Pure-FTPd"
  # ssl_verify: true
  # ssl_min_days_valid: 7
  # connect_timeout: 10
  # read_timeout: 10

tls picks how the session is encrypted:

user (with password) turns the check into a real login: USER, then PASS unless the server already answered 230. Without user the session stops after the greeting and the optional handshake.

ssl_verify: false accepts a certificate that does not validate, for servers with a self-signed certificate. Expiry is still reported and still checked against ssl_min_days_valid (set it to null to skip that).

Testing the data connection

By default the check never opens a data connection, so the passive port range does not have to be reachable. Setting transfer_path adds a full round trip -- upload, read back, compare, delete:

- type: "ftp"
  host: ftp.example.com
  user: "alice"
  password: "s3cret"
  transfer_path: "bigbrother-probe.txt"
  # transfer_content: "..."  # default: a unique payload per run

This is the only way to catch a server that greets, negotiates TLS and authenticates perfectly but cannot actually move bytes -- a full disk, a read-only mount, or a passive port range the firewall never opened. A plain host_ip check and an ftp check without transfer_path both stay green in all three cases.

Notes:

• The path is relative to the login directory, and these accounts are usually chrooted into a live document root, so pick a name that is obviously a probe and harmless to serve.
• The payload is unique per run unless transfer_content says otherwise, so a leftover file from an earlier run cannot make RETR succeed against a STOR that silently wrote nothing.
• The probe is deleted even when the check fails partway. The one case that can leave a file behind is a server that accepts STOR and then stalls, because it will not process the DELE while it is still waiting for the data connection; the next healthy run overwrites and removes it.
• PBSZ 0 and PROT P are negotiated first when the control connection is encrypted, so the data connection is encrypted too. Servers that additionally require the data connection to resume the control connection's TLS session (vsftpd's require_ssl_reuse) are not supported; pure-ftpd does not.

Notifiers

A list of available notifiers:

• telegram - Notify via Telegram's bot.
• console - Print all checks on your terminal.
• prometheus - Collect and expose Prometheus metrics.

Installation

make build-release
bin/bigbrother

Usage

bin/bigbrother -h
bin/bigbrother -c config.yml

Example config

See config.yml.sample.

Reload config dynamically

To reload bigbrother's config dynamically send signal SIGHUP to the running process.

kill -HUP $(pidof bigbrother)

Caveats:

• Checks already in flight are not cancelled and run to completion and may still notify under the old config
• No new checks are scheduled until the new App has taken over
• If the new config file is missing or invalid, the reload is discarded and the current config keeps running

Development

make build
bin/bigbrother

Testing

make test

Runs the spec suite (crystal spec). Some specs generate self-signed certificates on the fly (e.g. to test SSL certificate expiry checks) and require the openssl CLI to be installed. The suite also runs as a test job in CI (see .gitlab-ci.yml).

Contributing

1. Fork it ( https://github.com/splattael/bigbrother/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

Contributors

• splattael Peter Leitzen - creator, maintainer