chiamon VS node_exporter

I’m a bit of a monitoring nerd, and when I first got into chia I wrote the chia-exporter for Prometheus and put together chiamon, which just glues together a bunch of industry-standard monitoring tools (which I was already running anyways). Seeing people struggle with installing and configuring all that showed me that there’s a need for a simpler solution for less-technical people who only care about monitoring chia. More than I was willing or able to take on, so kudos. I probably don’t have a lot of time to help with your project either, but I’d be happy to help out where I can.

Hey, I also have something similar - but sadly not for plotting (yet).https://imgur.com/a/rPuqK3c.Used https://github.com/retzkek/chiamon and customized it a bit.

Thanks! I don't have the resources (or motivation) to test and package for all the different ecosystems that chia can run on. I myself am using a niche system - freebsd. If there was community interest in building it out maybe a github project could be in the future. Besides, there are already some great setups out there using grafana.

There are tools like ChiaMon that you could use; https://github.com/retzkek/chiamon

I use Grafana and Prometheus, with various exporters to collect metrics on everything. Add promtail and Loki for logs to really spice it up. See my example setup: https://github.com/retzkek/chiamon

The goal is to have some kind of dashboard (like chiamon) with all active/inactive plotters and be able to control them through the network. Ideally even upload the finished plots directly to the NAS through the network. Following the HiveOS example.

$ 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.