# CloudMon
CloudMon is a monitoring orchestrator for clouds. Cloudmon integrates directly an IaaS plataform (currently works with Apache CloudStack and AWS EC2) with a monitoring plataform (Zabbix).
On the fly, CloudMon will:
create, delete or change status of zabbix hosts (each host corresponds to an IaaS VM) and even update its configurations (templates, hostgroups, macros…) replicating the changes (created/removed/stopped) ocurred within the VMs.
Read VMs [resource tags](Tags.md) and take different actions based on its values.
Associate zabbix hosts to predefined templates or hostgroups.
Simultaneously monitor multiple Cloud regions (different or same IaaS).
CloudMon works as a Python Daemon that retrieves IaaS data through CloudStack API, AWS EC2 API and/or its event queues, processing that data and taking the proper action in Zabbix through the Zabbix API.
CloudMon requires a Zabbix Agent installed to ensure proper functionality.
CloudMon has been tested and used in CentOS environments and Python 2.7.
## Getting Started
Read the [documentation](https://cloudmon.readthedocs.io)
Recommended to create a python virtualenv for CloudMon.
Install via pip install cloudmon.
Edit your cloudmon.conf file for your needs. See [Configuration](Configuration.md).
Create and edit one or more [managers](Managers.md).
Edit /etc/init.d/cloudmon if needed.
Run CloudMon with: cloudmon or /etc/init.d/cloudmon start | stop | restart. See [Usage](Usage.md).
## Success Stories
CloudMon has been successfully used by Globo.com to monitor its Cloud Infrastructure.
# Changelog All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
Metadata
Release files for cloudmon 0.3.0
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 |
|---|---|---|---|---|
| cloudmon-0.3.0.tar.gz | 46.4 kB | Without provenance | Details for cloudmon-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cloudmon-0.3.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for cloudmon-0.3.0-py2.py3-none-any.whl |
Total release size: 99.4 kB
Release files / cloudmon-0.3.0.tar.gz
| Download URL | cloudmon-0.3.0.tar.gz |
|---|---|
| Size | 46.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33158b405a13275c84c87d0f067314025d3f5fd19f5f9bf7cf3c42775e94c9f7
|
|
BLAKE2b-256 checksum How to use checksums |
12d5f03c51378b1e998b7a7aa3ed23ae8456014f08678db312d88cd1fe55bf26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.10
|
Release files / cloudmon-0.3.0-py2.py3-none-any.whl
| Download URL | cloudmon-0.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 53.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f8b30489ef3f3b2f54d1002554c7f56f41ca333a5dda23395a7c326f67bbb070
|
|
BLAKE2b-256 checksum How to use checksums |
644d4ccf2228a111cb763ddd1023365b84f91f62b5efd6e98a03c525b5ed6a61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/39.2.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.10
|
Security for cloudmon 0.3.0
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.