I recommend to use bacula_stats (CLI version of bacula_monitor) instead. With bacula_monitor we had to chown a+rx on /etc/bacula our config files, which is a security risk, considering an attacker who managed to gain access to the user http could've read the secret bacula key. There's a workaround to not change bacula config files' permission (populating to an intermediate DB by a root daemon), but using the CLI version is advantageous, because it's simpler, easier to deploy and distribute and securer.

Displays most recent successful job for each client's fileset pools on one page and additionally compares it to your configured jobs to show by markup, whether a backup is missing. Moreover you can configure for defined pools a timeout value (in days), after that the backup should be marked up as old (yellow). Your config file (you have to specify the path in functions.py) will be parsed for the configured clients and thus checked for connectivity on port 9102, to indicate whether your client's bacula service is up or down.

Django >= 1.8.4
netcat
psycopg2
PyYAML
voluptuous
nginx (with uwsgi) or apache2 (with mod_wsgi)
Optionally (recommended):
virtualenv

The python web framework django is required. I run this web app in a virtualenv with apache, but you can also run it without a virtualenv. Check the provided apache example config out, which i setup for my virtualenv.
If you decide to use virtualenv. Here's one info link:
https://www.jeffknupp.com/blog/2012/02/09/starting-a-django-project-the-right-way/
See the requirements above, that have to be installed for bacula_monitor to work.

mkdir -p /var/log/django/ chown -R wwwrun /var/log/django/ (where wwwrun is the user who runs wsgi (depending on your distro webserver package/setup it might be wwwrun, http or another user))

See bm.conf example config file for available settings. Make sure to restart your webserver after editing the config file.