trustlines-watch
trustlines-watch helps monitoring the trustlines cluster. It watches a running parity or geth client via the JSONRPC interface and pushes information to a riemann instance.
Installation
trustlines watch requires python 3.6 or up. It also needs the postgresql development files. On a debian based system these can be installed with
apt install libpq-dev
Please run the following command in a python 3 virtualenv:
pip install . -c constraints.txt
This will install a ‘tl-watch’ executable.
Usage
tl-watch etherscan
Watches etherscan for the current blockNumber. Run tl-watch etherscan --help for available command line options.
tl-watch jsonrpc
Watches a parity or geth client via the JSONRPC interface. Run tl-watch jsonrpc --help for available command line options.
tl-watch relay
Watches a trustlines relay server via the REST API. Run tl-watch relay --help for available command line options.
tl-watch psql
Queries a postgres database. Run tl-watch psql --help for available command line options. The sql query to run is given via the command line option --sqlquery. It must return at least the service and metric fields.
Here’s an example that would monitor the synchronization state of ethindex:
tl-watch psql --sqlquery "select 'sync.' || syncid || '.last_block' service, last_block_number metric from sync"
tl-watch get-website-hash
Calculates the hash of the relevant sources from a specific URL (--url). This is meant to be used in combination with tl-watch website to get the initial origin hash value. Relevant are sources which can change the content of the website. Therefore the hash gets calculated over the basic HTML and the first parity JS scripts. Stylesheets are not relevant for the content. External JavaScript can’t be ensured to not change and must not affect the content on its own. Run tl-watch get-website-hash --help for available command line options.
tl-watch website
Watches for changed code of a website. It continuously calculates the hash of the relevant sources to ensure they haven’t changed in comparison to an initially provided origin hash. That origin hash can be calculated with tl-watch get-website-hash. Run tl-watch website --help for available command line options.
Change log
See CHANGELOG.
1 maintainer
Metadata
1 maintainer
Release files for trustlines-watch 0.5.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 | |
|---|---|---|---|---|
| trustlines-watch-0.5.6.tar.gz | 12.4 kB | Without provenance | Details |
Release files / trustlines-watch-0.5.6.tar.gz
| Download URL | trustlines-watch-0.5.6.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97426a484cab07f242268cc300914a150236f0bad44036f1f590abe9c8ff78a2
|
|
BLAKE2b-256 checksum How to use checksums |
3dae72a8416e8fe9aaf8a2aca6ea4074c970fc93d2e77ef9f74142132f3000ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.10.0 pkginfo/1.2.1 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.5 CPython/3.6.8
|
Security for trustlines-watch 0.5.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.
