moosefs-tricorder
Scrape a moosefs master server with mfscli and export information to prometheus for further processing - graphing, alerting, etc.
I couldn't find documentation about the moosefs master's API. However, they do provide the mfscli command, and its output is parseable relatively easily.
I don't guarantee this will work with any version of the master other than 3.116, that's all I've tested it on.
Installation
You have three options
- Install it via
pip install moosefs-tricorderon a machine. You may run into irritations due to dependencies. You will also need to installmfscli- the exporter uses that to probe the master for statistics about the master, the chunkservers, and the moosefs filesystem. - Use my docker image -
docker run -p 9877:9877 unixorn/moosefs-tricorder moosefs-prometheus-exporter --master YOUR_MOOSEFS_MASTER. This image supports the linux/arm64, linux/amd64 and linux/arm/v7 architectures. - Bake your own image with
make local. You'll need to change$HUB_USERin theMakefile.
Usage
If you install directly on your system, you can run moosefs-prometheus-exporter.
[--master-port MASTER_PORT (default 9421)] [--moosefs-master MOOSEFS_MASTER] [--polling-interval POLLING_INTERVAL_IN_SECONDS (default 15)]
If you're running it in docker, you can either run docker run -p 9877:9877 unixorn/moosefs-tricorder moosefs-prometheus-exporter --master YOUR_MOOSEFS_MASTER, or use docker-compose.
---
# example docker-compose.yaml
version: '3'
services:
moosefs-tricorder:
image: unixorn/moosefs-tricorder:latest
container_name: moosefs-tricorder
command: moosefs-prometheus-exporter --moosefs-master=mfsmaster.example.com
ports:
- 9877:9877
restart: unless-stopped
environment:
- TZ=America/Denver
volumes:
- /etc/hostname:/etc/hostname:ro
- /etc/localtime:/etc/localtime:ro
- /etc/timezone:/etc/timezone:ro
Metadata
Release files for moosefs-tricorder 0.1.0
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 | |
|---|---|---|---|---|
| moosefs_tricorder-0.1.0.tar.gz | 6.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moosefs_tricorder-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / moosefs_tricorder-0.1.0.tar.gz
| Download URL | moosefs_tricorder-0.1.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86b271c40289182a7489530a5a25c79872c22c736fc2e1a3016aadd4a99ae221
|
|
BLAKE2b-256 checksum How to use checksums |
af586288a2e108192cfef7d3760711918573d444d586c23db4d56c4e7d5dfd37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.9.17 Darwin/23.0.0
|
Release files / moosefs_tricorder-0.1.0-py3-none-any.whl
| Download URL | moosefs_tricorder-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d08f6a5084ca573cbdd5292dd9f27f858a921e19616c52bd2db4a4761d704938
|
|
BLAKE2b-256 checksum How to use checksums |
c2ef5b2961c0e2860339812e5a2d384a21f53649d4d4fb2c622b53069bc816f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.9.17 Darwin/23.0.0
|
Security for moosefs-tricorder 0.1.0
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.