ftw.publisher.monitor
This package is an ftw.publisher addon for monitoring the publisher queue and alerting when the queue cannot be processed for some reason.
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.
Upgrade 2.0
First you need to install the profile ftw.publisher.monitor:default. The profile hasn’t existed before and because after the installation of a profile all upgradesteps are shown as installed, you have to run it manually or have to reenter the data in the config panel.
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
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.
Changelog
2.0.3 (2020-09-01)
New Mailhost needs a explicit charset. [mathias.leimgruber]
2.0.2 (2020-09-01)
Fix sending actual emails with plone 5. [mathias.leimgruber]
2.0.1 (2020-08-04)
Add uninstall profile. [djowett-ftw]
2.0.0 (2020-06-11)
Add Plone 5 compatibility [Nachtalb]
Migrate config from annotation to registry storage [Nachtalb]
1.1.2 (2017-11-15)
Clarify and fix help texts in control panel. [jone]
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
Metadata
Release files for ftw.publisher.monitor 2.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ftw.publisher.monitor-2.0.3.tar.gz | 19.6 kB | Without provenance | Details for ftw.publisher.monitor-2.0.3.tar.gz |
Release files / ftw.publisher.monitor-2.0.3.tar.gz
| Download URL | ftw.publisher.monitor-2.0.3.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcfb41a5254d53a46f012c829aaf6261b03aa43461b0ac16d97053eac23f8fbe
|
|
BLAKE2b-256 checksum How to use checksums |
b50dd1d2c25dd5fa319b60098698ae08c6d52ae0ef92a2c9b9caa68f0bb4be53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/2.7.17
|
Security for ftw.publisher.monitor 2.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.