node_exporter VS windows_exporter

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

if you want to monitor your windows machine you can install a windows exporter from here. After installing you can start the service to start the windows exporter

The windows_exporter iis module has a number of app pool metrics.

Check out the windows_exporter. It uses native OS calls instead of WMI where it can to reduce overhead.

Would this do what you're asking for? https://github.com/prometheus-community/windows_exporter

Windows-exporter => InfluxDB => Grafana which displays on a 10” tablet in the lounge. I know what the normal CPU, RAM, Disk write number should be so it’s easy to see everything is good at a glance. Grafana dashboard.

Try the windows exporter. It uses native calls for a lot of the common data gathering. Much more efficient than WMI.

Try windows_exporter with process-collector whitelist https://github.com/prometheus-community/windows_exporter/blob/master/docs/collector.process.md

I deployed Prometheus Windows Exporter on AKS (Kubernetes v. 1.24.6) using the following instructions: https://github.com/prometheus-community/windows_exporter/blob/master/kubernetes/kubernetes.md