node_exporter VS plotman

$ wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz $ tar -xzvf node_exporter-1.7.0.linux-amd64.tar.gz

Node Exporter

The Prometheus node_exporter can provide this information, doesn't require root. You could run it as a systemd user unit if you don't have root.

I personally find it best to learn through experimentation. Start with reading a bit about Prometheus and Grafana through their docs, and then familiarise yourself with setting up a local Prometheus + Grafana instance either locally or with docker using docker-compose, along with something to generate /metrics endpoint for Prometheus to scrape from such as a custom Prometheus exporter in Python or using Node Exporter.

Your best bet might be to fork node_exporter to get you more verbose socket stats: https://github.com/prometheus/node_exporter/blob/master/collector/sockstat_linux.go

I use Grafana + Prometheus + Node Exporter.

Crazy idea, can't NX devices run Docker? I wonder if the node_exporter would work.

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.

You may setup node exporter and collect metrics with prometheus for example. Its not quite "simple" way, but still you may find it useful.

Yes, see https://github.com/madMAx43v3r/chia-plotter for plotting with a ramdisk and https://github.com/ericaltendorf/plotman to automate everything.

Plotman is what you want. You can plot on multiple drives (tmp), then cache the completed plots on destination drives/directories (dst). Then the archive function can rsync them to an array of archive drives. Very easy to modify the config .yaml file then run "plotman plot" and "plotman archive". https://github.com/ericaltendorf/plotman

Plotman: v0.5.1

Yeah. Plotman config guide shows you how to set it up for madmax. Its as easy as changing the "type" variable in the config file from "chia" to "madmax" and then changing your other plotting variables to what they should be be for madmax.

Madmax plotter, Swar plot manager, and Plotman plot manager all support portable plots for pools now. Others probably do, but I'm not as familiar with them. Update to the latest versions for the best results, and double-check your configuration files as some settings may have changed since your last update. And you can also use plot managers with Madmax these days, if you want to take advantage of workflow management (multiple destination drives, parallel plotting on bigger plotters, less scrolly logs, etc).

The v0.5 plotman includes support for madmax plotting as well as chia pool plotting. If you're feeling brave, update your plotman with: pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@main

from the default config:

# upgrading chia to the latest version cd chia-blockchain/ . ./activate chia stop -d all deactivate git fetch git checkout latest git reset --hard FETCH_HEAD git status sh install.sh . ./activate chia init edit file: nano /home/YOURUSERNAMEHERE/chia-blockchain/setup.py change the chiapos==1.0.2 to chiapos # resolving all config problems sudo apt install aptitude sudo aptitude -f install build-essential aptitude install cmake sudo aptitude install cmake (first type n, then type y) sudo aptitude install python3-dev (first type n, then type y) cd git clone --branch combined https://github.com/pechy/chiapos.git cd chiapos mkdir -p build && cd build # configuring flags to compile CFLAGS="-mtune=native -march=native" CXXFLAGS="-mtune=native -march=native" cmake ../ 1241 cmake --build . -- -j 6 # compiling cmake --build . -- -j 6 . ~/chia-blockchain/activate cd ~/chiapos && python setup.py install # finding all old chiapos files to replace find / -name chiapos.cpython-38-x86_64-linux-gnu.so # removing old chiapos rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so rm /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos.cpython-38-x86_64-linux-gnu.so cp /home/YOURUSERNAMEHERE/chiapos/build/chiapos.cpython-38-x86_64-linux-gnu.so /home/YOURUSERNAMEHERE/chia-blockchain/venv/lib/python3.8/site-packages/chiapos-0.0.0-py3.8-linux-x86_64.egg/chiapos.cpython-38-x86_64-linux-gnu.so # reinstall plotman pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@development plotman interactive in plot logs you should be able to see Using optimized chiapos - 24288eb