Python Monitoring Server
Currently under active development. It aims to be a generic solution for logging events and creating aggregate reports.
Installing Development Environment
git clone git://github.com/philipcristiano/pms.git
cd pms
make bootstrap && make deploy
Deploying PMS
PMS can be deployed as a WSGI app. Once installed the app is available as pms.app:app and can be run with gunicorn or a WSGI server of your choice.
Configuration
PMS will look for a config file at /etc/pms/pms.conf
You config file would look something like this:
[mongodb] host=33.33.33.10
- [aggregation]
- [[host-level]]
properties=host,level
- [[random]]
properties=level
You need to define a host for Mongo.
The aggregration properties are to define the rollups. The second level is the name of the rollup and properties is a list of fields to rollup. PMS will attempt to rollup any events added. The event will be rolled up if it has properties matching the set defined for a rollup.
Recording Events
Events are recorded by posting a JSON document to /record. If you include all fields for an aggregate rollup it will create/update the corresponding record.
Sample:
curl -v -X POST http://localhost/record -H “Content-Type: application/json” -d ‘{“key”: “value”}’
Metadata
Release files for pms 0.1.6
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 |
|---|---|---|---|---|
| pms-0.1.6.tar.gz | 269.9 kB | Without provenance | Details for pms-0.1.6.tar.gz |
Release files / pms-0.1.6.tar.gz
| Download URL | pms-0.1.6.tar.gz |
|---|---|
| Size | 269.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dc54f0ddd1f5ab566e3e318391b41bf031f3ba8714f7f25b9e2de3540377ca9
|
|
BLAKE2b-256 checksum How to use checksums |
aa512a8fdc9318ae48fd4975849441c0b12529b5150dc219083fbba358841b35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pms 0.1.6
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.