ftw.publisher.monitor 1.1.1

Usage

• Add ftw.publisher.monitor to your buildout configuration on the editoral site and run bin/buildout:

[instance]
eggs +=
    ftw.publisher.sender
    ftw.publisher.monitor

• Configure the report in the publisher control panel.

Failed extraction monitoring

When the publisher is set up with an asynchronous extraction queue (e.g. with redis), the extraction may break. This is possible because the extraction is asynchronous and thus not in the same transaction as the publisher job is created. Therefore creating the publisher job may work, but executing the extraction job may fail.

For mitigating that problem we are monitoring the jobs and warn whenever a job has still a 0-sized job file and the job file is older than the configured threshold.

Links

• github project repository: https://github.com/4teamwork/ftw.publisher.monitor

• Main publisher github project repository: https://github.com/4teamwork/ftw.publisher.sender

• Issues: https://github.com/4teamwork/ftw.publisher.monitor/issues

• Pypi: http://pypi.python.org/pypi/ftw.publisher.monitor

• Continuous integration: https://jenkins.4teamwork.ch/search?q=ftw.publisher.monitor

Copyright

This package is copyright by 4teamwork.

ftw.publisher.monitor is licensed under GNU General Public License, version 2.

1.1.1 (2017-11-15)

• Add support for monitor failed exctractions. [jone]

• Drop Plone 4.2 support. [jone]

• Drop compatibility with Plone 4.1. Add compatibility with Plone 4.3. [mbaechtold]

1.0 (2011-01-19)

• Initial release