HEM - HTTP Endpoint Monitor
To install hem, use:
pip install hemApp
Command line syntax:
Usage: hem [OPTIONS]
Options:
--version Show the version and exit.
-v, --verbose Verbose mode, multiple -v options increase verbosity.
-c, --config PATH Specifies an alternative config file
--help Show this message and exit.
By default hem will use a config file called hem.yaml in the current directory or /etc/hem.yaml unless one is specified with the --config option.
Config syntax
The config.yaml is made up of sections:
- settings - general settings
frequency: 30 // Frequency to run tests
- metrics - Where to store the results of the testing e.g. graphite:
type: graphite // Name of plugin to use
server: 127.0.0.1 // IP or hostname of server
port: 2003 // Port to use
- tests - the actual endpoints to test
test-name:
path: Path to test
secure: Is this using HTTPS?
hosts: List of hosts to use
certificate: Path to keypair to use for mTLS - must be un-encrypted
discovery: discovery block for this test - merged with top level block
- discovery - optional top level discovery config shared across tests
type: dns // Plugin to use
Metadata
Release files for hemApp 11
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 |
|---|---|---|---|---|
| hemApp-11.tar.gz | 17.2 kB | Without provenance | Details for hemApp-11.tar.gz |
Release files / hemApp-11.tar.gz
| Download URL | hemApp-11.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c588f85e52e234f79cec80f65598e5cd5a3e8f7c373cbca3fd72e6f158cfb38a
|
|
BLAKE2b-256 checksum How to use checksums |
127efafa15864f9ca493cece54d055605211acdecad34226c920e111cc0fd9e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.6.1 requests/2.25.1 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.5.10
|
Security for hemApp 11
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.