exploring-rust-ecosystem VS windows_exporter

In this article, I’ll show you how to set up monitoring of a Rust web application. The application will expose Prometheus metrics that will be visualized using Grafana. The monitored application is mongodb-redis demo described in detail here. Finally, the following architecture will be obtained:

The project is implemented with MongoDB Rust driver and redis-rs crate.

gRPC server

Source code

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