TL;DR: Add hume commands inside your scripts to better report to a central location. Currently supporting Slack, syslog, remote-syslog, logstash, etc
Imagine this: You have some cron scripts. They need to run correctly, and you need to know if anything happens. You usually check logs via email or some cool dashboard. Yeah. But it gets boring, repetitive and you end up not checking the logs. It is a well known sysadmin syndrome.
Hume client works and can be used in bash scripts, or during a screen session, to provide real time updates to your managers, customers, etc.
So, for instance write those scripts adding hume commands in them:
1 maintainer
Metadata
1 maintainer
Release files for humed 1.2.28
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 |
|---|---|---|---|---|
| humed-1.2.28.tar.gz | 20.1 kB | Without provenance | Details for humed-1.2.28.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| humed-1.2.28-py3-none-any.whl | Python 3 | none | any | Details for humed-1.2.28-py3-none-any.whl |
Total release size: 40.1 kB
Release files / humed-1.2.28.tar.gz
| Download URL | humed-1.2.28.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff3c1aabf5f25bf57e141f2ff98f891c5a5847d68d4b8d479930aed2e84a58c6
|
|
BLAKE2b-256 checksum How to use checksums |
a027e152c7c32ecd9fc2417c580024cd1e39c57e99d88cd0ab258db5bc496828
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.18.4 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.6.5
|
Release files / humed-1.2.28-py3-none-any.whl
| Download URL | humed-1.2.28-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c7a16198ca5f9696a4cc780367ffad9f0bca7c053eae924466c96139d55a8fe
|
|
BLAKE2b-256 checksum How to use checksums |
76f42cff00f136464d300c4b17504983d06e092a5c88031f69b1b0f38af31451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.18.4 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.6.5
|
Security for humed 1.2.28
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.
