Alignak Backend Modules
Alignak modules for the Alignak Backend
Installation
The installation of this module will copy some configuration files in the Alignak default configuration directory (eg. /usr/local/etc/alignak). The copied files are located in the default sub-directory used for the modules (eg. arbiter/modules).
From PyPI
To install the module from PyPI:
sudo pip install alignak-module-backend
From source files
To install the module from the source files (for developing purpose):
git clone https://github.com/Alignak-monitoring-contrib/alignak-module-backend cd alignak-module-backend sudo pip install . -e
Note: using `sudo python setup.py install` will not correctly manage the package configuration files! The recommended way is really to use `pip`;)
Short description
This meta-module for Alignak contains 3 modules:
Arbiter module, which features are:
get configuration from Alignak backend
manages acknowledgements, downtimes schedule and re-checks
Scheduler module, which features are:
manage retention (load and save)
Broker module, which features are:
update live state of hosts and services in the Alignak backend
update log for hosts and services checks in the Alignak backend
Configuration
Each module has its own configuration file and its configuration parameters. The configuration files are documented to help setting the right configuration.
Arbiter module:
configure the Alignak backend connection (url and login)
configure periodical configuration modification check
configure periodical required actions (ack, downtime, …)
Scheduler module:
configure the Alignak backend connection (url and login)
Broker module:
configure the Alignak backend connection (url and login)
Bugs, issues and contributing
Contributions to this project are welcome and encouraged … issues in the project repository are the common way to raise an information.
Metadata
Release files for alignak_module_backend 1.4.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 |
|---|---|---|---|---|
| alignak_module_backend-1.4.3.tar.gz | 66.4 kB | Without provenance | Details for alignak_module_backend-1.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alignak_module_backend-1.4.3-py3-none-any.whl | Python 3 | none | any | Details for alignak_module_backend-1.4.3-py3-none-any.whl |
Total release size: 102.6 kB
Release files / alignak_module_backend-1.4.3.tar.gz
| Download URL | alignak_module_backend-1.4.3.tar.gz |
|---|---|
| Size | 66.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc395ea9e0526fed6e78f340da1287e10b0bc6df0cf18fc4bc4d07892ae5d09c
|
|
BLAKE2b-256 checksum How to use checksums |
b69ce0dde635704a1d878cbbe1df329144ddcccc71acde3517279eb495f61725
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.3
|
Release files / alignak_module_backend-1.4.3-py3-none-any.whl
| Download URL | alignak_module_backend-1.4.3-py3-none-any.whl |
|---|---|
| Size | 36.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b414934c0ebd76f89b9581c3efce9592e7bc350dc0028baa032376df0b4da02
|
|
BLAKE2b-256 checksum How to use checksums |
290bdbe7442d81b2c9b16773f0fc3837bd9c6e267a8187914d9d24f0964e58f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.6.3
|
Security for alignak_module_backend 1.4.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.