rustlings-solutions-5 VS node_exporter

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/

i think you've found what i'm looking for! https://github.com/rust-lang/rustlings

I would recommend rustlings as a way to get used to semantics. It starts from absolute basics but it gave me a more intuitive understanding of the language.

go along with Rustlings https://github.com/rust-lang/rustlings

rustlings — Small exercises to get you used to reading & writing Rust code!

I had finished this Udemy course, which was a bit too fast towards the end but still enjoyable, I read THE BOOK and done the Rustlings (here are my old solutions and here the new ones).

You will get used to it when you write more Rust code. Read the book, implement some exercises and watch some tutorial YT videos, everything will make sense eventually.

Check out rustlings. Simple exercises with writing rust code, introducing new concepts along the way.

There's an official "book" that you can look up online. It goes through Rust step by step, like a tutorial. Alternatively there's the rustling's course where you learn Rust by doing small exercises. I have only ever looked at the book, which is fantastic. But if you know a bit of C and some sort of class-system like in OOP or Haskell's typeclasses you can just look up the syntax when you need to, it is really easy. Also, the compiler warnings/errors usually tell you what you need to do in order to fix your error (especially for simple stuff in the beginning) so often you don't even need to google the issue.

Rustlings might be useful to you: https://github.com/rust-lang/rustlings

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