Description
Checks web apps health.
Install
Linux:
sudo pip3 install webapp_health_check --upgrade
Also is possible to use:
sudo python3 -m pip install webapp_health_check --upgrade
On windows with python3.5:
pip install webapp_health_check --upgrade
For proxies add:
--proxy='http://user:passw@server:port'
Usage
Use the command line:
> webapp_health_check --help
usage: webapp_health_check [-h] [-u [URL]] [-a [APP_NAME]] [-e [EXTRA_ARGS]]
optional arguments:
-h, --help show this help message and exit
-u [URL], --url [URL]
url to check
-a [APP_NAME], --app_name [APP_NAME]
app_name is the key entry where the description is located
-e [EXTRA_ARGS], --extra_args [EXTRA_ARGS]
extra args
Example usage
Example use:
> webapp_health_check -u “https://xxx/” -a process_app_name
{“status”:”Healthy”,”totalDuration”:”00:00:02.4136092”,”entries”:{“process_app_name”:{“data”:{},”description”:”Process health check was successful.”,”duration”:”00:00:02.4106469”,”status”:”Healthy”}}}
Nagios config
Example command:
define command{
command_name webapp_health_check
command_line /usr/local/bin/webapp_health_check -u "$ARG1$" -a "$ARG2$" --extra_args='$ARG3$'
}
Example service:
define service {
host_name SERVERX
service_description service_name
check_command webapp_health_check!http://url/!process_app_name
use generic-service
notes some useful notes
}
You can use ansible role that already has the installation and command: https://github.com/CoffeeITWorks/ansible_nagios4_server_plugins
Metadata
Release files for webapp-health-check 1.5
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 |
|---|---|---|---|---|
| webapp_health_check-1.5.tar.gz | 5.5 kB | Without provenance | Details for webapp_health_check-1.5.tar.gz |
Release files / webapp_health_check-1.5.tar.gz
| Download URL | webapp_health_check-1.5.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21374678b397dee68e20409aaaec243415b01d9b60d9d0cc33c9b0f7851fdfd8
|
|
BLAKE2b-256 checksum How to use checksums |
378dd02ff02125e97165ca0dce57ca208fadaf1750bf8def028da83a47fa74a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.4.2 requests/2.22.0 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.19.7 CPython/3.5.2
|
Security for webapp-health-check 1.5
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.