xbus.monitor 0.2.1

Xbus

Xbus is an Enterprise service bus. As such it aims to help IT departments achieve a better application infrastructure layout by providing a way to urbanize the IT systems.

The goals of urbanization are:

• high coherence

• low coupling

More information about Xbus:

• Documentation: <http://xbusbroker.readthedocs.org/>

• Website: <http://xbus.io/>

• Presentation: <http://bit.ly/1AYtQa6>

Installing

Set up a virtualenv:

$ mkvirtualenv -p /usr/bin/python3 xbus

Install the xbus.monitor package:

$ pip install xbus.monitor

Configuring

Follow the xbus.broker README file to set it up.

Xbus monitor settings are within the etc/production-example.ini file; grab it from bitbucket (eg for the 0.1.2 version):

$ wget https://bitbucket.org/xcg/xbus.monitor/raw/0.1.2/etc/production-example.ini -O monitor.ini

Edit the file following comments written inside.

Localization:

Edit the “pyramid.default_locale_name” variable. Note: Only “en_US” and “fr_FR” are supported for now.

Running

Run as a regular Pyramid program:

$ pserve monitor.ini

Run tests

nosetests

Development

When running the monitor for development purposes, it is recommended to deactivate the cookie.secure option in the configuration file:

cookie.secure = false

Generate the translation template

pip install Babel lingua
python setup.py extract_messages

Other translation tasks

See <http://docs.pylonsproject.org/projects/pyramid/en/latest/narr/i18n.html>.

python setup.py [init_catalog -l en_US] [update_catalog] [compile_catalog]

Thanks

xbus.monitor uses the following external projects; thanks a lot to their respective authors:

• pyramid <http://docs.pylonsproject.org/projects/pyramid/en/latest/>

• pyramid_httpauth <https://github.com/tarzanjw/pyramid_httpauth>

0.2.1 (2016-07-04)

• Fix inclusion of the monitor_js client-side app into the package.

0.2.0 (2016-06-27)

• Add new consumer event type settings (related to optional data lookup” / clearing features).

• Resolve aiozmq endpoints beforehand.

• Safer consumer getter.

• Log Xbus requests by default in the example configuration file.

• Simplified deployment; this application now includes a default client.

• Reworked the login system to apply on the whole client app instead of triggering on specific JS requests.

• Adapt to message tracking changes done in xbus.broker.

0.1.4 (2015-05-25)

• Event types: Allow setting the “immediate reply” flag.

• Update requirements.

0.1.3 (2015-05-18)

• Define required package versions in setup.py and document why some are frozen.

0.1.2 Initial release (2015-05-12)

• Initial implementation of the Xbus monitor.