Collector
Collector is a Django application to collect monitoring data samples through HTTP or SNMP GET interface. Collected data might be then visualized using e.g. Grafana.
Dependencies
Collector uses InfluxDB time series database for storing monitoring data samples and django supported database for storing configuration and Redis broker.
Quick start
Assuming InfluxDB is properly configured (setting up authentication is recommended) and so is Redis broker just a few steps are required.
Install watcheye-collector:
$ pip install watcheye-collectorAdd collector application to INSTALLED_APPS setting.
INSTALLED_APPS = [ ... 'collector', ]Integrate Celery with your django project (see Celery documentation for further reference).
Add InfluxDB connection and Celery configuration in settings.py file:
INFLUXDB_HOST = 'my_host' INFLUXDB_USERNAME = 'user' INFLUXDB_PASSWORD = 'secret' CELERY_BEAT_SCHEDULE = { 'snmp-scheduler': { 'task': 'collector.tasks.snmp_scheduler', 'schedule': crontab(minute='*') } } CELERY_RESULT_BACKEND = 'redis://my_broker_host/0' CELERY_BROKER_URL = 'redis://my_broker_host/1' # to use non-default values configure also: INFLUXDB_PORT = 1234 INFLUXDB_DATABASE = 'my_database' INFLUXDB_RETENTION_POLICY = 'my_policy' INFLUXDB_DURATION = '30d'To set InfluxDB instance up run:
python manage.py setupinfluxdb --username <admin_username>To create the collector models run:
python manage.py migrateInclude the collector URLconf in your project urls.py:
path('collector/', include('collector.urls')),Start the development server and visit http://127.0.0.1:8000/admin/ to create a collector configuration (the Admin application must also be enabled).
Run Celery worker with:
celery --beat --app <my_project> workerPOST some samples:
$ curl -i -X POST \ -H "Content-Type: application/json" \ -d '{"host":"test", "timestamp": 1500000000, "samples": [{"parameter":"CPU", "value": 10}]}' \ http://127.0.0.1:8000/collector/
Metadata
Release files for watcheye-collector 2.0.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 | |
|---|---|---|---|---|
| watcheye-collector-2.0.0.tar.gz | 25.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| watcheye_collector-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.1 kB
Release files / watcheye-collector-2.0.0.tar.gz
| Download URL | watcheye-collector-2.0.0.tar.gz |
|---|---|
| Size | 25.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ebe7a105dce429ebe9c9d0589d59682bd6d3efc9f82c6d743f526ed2010c8c0
|
|
BLAKE2b-256 checksum How to use checksums |
bacb974af5731a6b0c077d088ede0418c167f9c8296e7e7e96a2a14e7438db26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Release files / watcheye_collector-2.0.0-py3-none-any.whl
| Download URL | watcheye_collector-2.0.0-py3-none-any.whl |
|---|---|
| Size | 32.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5a9f2e62b7b3fcd9bd2ec3ee86067099b490e8e475cf988d760fa5a4ce0486b
|
|
BLAKE2b-256 checksum How to use checksums |
a4b6dae78197bab842b4880740b9860426740295cd4f15d9eb0c3511712fe43d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Security for watcheye-collector 2.0.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.