Supervisor Gague Event Listeners
Version
v0.0.2
Supported Backend
Ali CMS
Baidu BCM
How to Use
create a config file
docker:
version: auto
supervisor:
SUPERVISOR_SERVER_URL: http://localhost:9000/RPC2
# SUPERVISOR_USERNAME: chulai-usr
# SUPERVISOR_PASSWORD: chulai-pwd
plugins:
# echo: {}
# ali_cms:
# user_id: ALI-USER-ID
# baidu_bcm:
# access_key: BCE_ACCESS-KEY
# secret_key: BCE-SECRET-KEY
# user_id: BCE-USER-ID
# scope: BCM-SCOPE
logging:
version: 1
loggers:
supergauge.eventlistener:
handlers: [file]
level: DEBUG
__main__:
handlers: [file]
level: INFO
handlers:
file:
class : logging.handlers.RotatingFileHandler
level: DEBUG
formatter: precise
filename: log/gauge.log
maxBytes: 1024
backupCount: 3
formatters:
precise:
class: logging.Formatter
format: "%(asctime)s %(name)-15s %(levelname)-8s %(processName)-10s %(message)s"
put following snippet in your supervisor config file
[eventlistener:supergauge]
command=supergauge /path/to/config/file
events=TICK_60 ; collect every 60s [TICK_5, TICK_60, TICK_3600]
user=username ; if you have your permission screwed up, use root
How to Install
pip install supergauge –process-dependency-links
Metadata
Release files for supergauge 0.0.2
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 | |
|---|---|---|---|---|
| supergauge-0.0.2.tar.gz | 10.7 kB | Without provenance | Details |
Release files / supergauge-0.0.2.tar.gz
| Download URL | supergauge-0.0.2.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55597978b392fdbe028accd59831813e24e1285974a232c76eda63ba6030560a
|
|
BLAKE2b-256 checksum How to use checksums |
98f62997062696a349b394a13ac512d4d305e16d981221907ca9e429345f911c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for supergauge 0.0.2
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.