docker-stats
docker stats wrapper which prints output in json
Usage
Install from PyPI and run
usage: docker-stats [-h] [-a] [container [container ...]] docker stats, json way positional arguments: container IDs or NAMEs of desired containers optional arguments: -h, --help show this help message and exit -a, --all get stats of all available containers -n, --normalize try to normalize stats
Normalization
Raw output of docker-stats is smth like this:
{
"my_container": {
"blkio_stats": {
"io_merged_recursive": [],
"io_queue_recursive": [],
"io_service_bytes_recursive": [
{
"major": 253,
"minor": 5,
"op": "Read",
"value": 7020544
},
{
"major": 253,
"minor": 5,
"op": "Write",
"value": 0
},
*SNIP*
]
}
}
}
As one can mention, there are an array object inside key io_service_bytes_recursive and each element of that array is flattened JSON with key op within values. That behaviour may occur in other keys.
docker-stats called with key --normalize tries to jsonify that to:
{
"my_container": {
"blkio_stats": {
"io_merged_recursive": [],
"io_queue_recursive": [],
"io_service_bytes_recursive": {
"Read": {
"major": 253,
"minor": 5,
"value": 7020544
},
"Write": {
"major": 253,
"minor": 5,
"value": 0
},
*SNIP*
}
}
}
}
Metadata
Release files for docker-stats 0.0.3
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 |
|---|---|---|---|---|
| docker-stats-0.0.3.tar.gz | 2.4 kB | Without provenance | Details for docker-stats-0.0.3.tar.gz |
Release files / docker-stats-0.0.3.tar.gz
| Download URL | docker-stats-0.0.3.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6dee5918ff1d2ad7062702c7931c4c16e6771935c7154258c13ca97d6ea62867
|
|
BLAKE2b-256 checksum How to use checksums |
2ef1a93f017ad89dbfea5de15ee640c4f32cec9b708c9eb003f87d82c3c9c417
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for docker-stats 0.0.3
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.