windows_exporter VS rust-prometheus

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

I used the prometheus library because it was the most popular and easiest to find. Some unusual and unexpected aspects were that, to delete metrics, all labels must be specified at once, and to record metrics, I always needed the full list of labels that were used during creation. However, these issues were manageable.

[dependencies] prometheus = { git = "https://github.com/tikv/rust-prometheus", rev = "ac86a264223c8d918a43e739ca3c48bb4aaedb90", features = ["process"] }

Metrics exposition is implemented with prometheus crate.

The new Elasticsearch exporter is written in the Rust programming language and is open-sourced on GitHub: github.com/vinted/elasticsearch-exporter-rs. The exporter uses asynchronous Tokio runtime, Rust Prometheus instrumentation library and the official Elasticsearch client library. Metrics collection is decoupled from the serving /metrics endpoint. In addition, Elasticsearch time-based metrics in milliseconds are converted into seconds to comply with Prometheus best practices (metrics ending in “millis” are replaced by “seconds”, “_bytes” and “_seconds” and postfixes are added where appropriate).

Rust has a popular binding: https://github.com/tikv/rust-prometheus