windows_exporter VS cadvisor

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

cAdvisor

https://github.com/google/cadvisor exports Prometheus metrics, but also offers a simple web-ui for container metrics.

version: '3' volumes: prometheus-data: driver: local grafana-data: driver: local services: prometheus: image: prom/prometheus:latest container_name: prometheus ports: - "9090:9090" volumes: - /etc/prometheus:/etc/prometheus - prometheus-data:/prometheus restart: unless-stopped command: - "--config.file=/etc/prometheus/prometheus.yml" grafana: image: grafana/grafana:latest container_name: grafana ports: - "3000:3000" volumes: - grafana-data:/var/lib/grafana restart: unless-stopped node_exporter: image: quay.io/prometheus/node-exporter:latest container_name: node_exporter command: - '--path.rootfs=/host' pid: host restart: unless-stopped volumes: - '/:/host:ro,rslave' cadvisor: # TODO: latest tag is not updated, check latest release https://github.com/google/cadvisor/releases image: gcr.io/cadvisor/cadvisor-arm:v0.47.0 container_name: cadvisor ports: - "8080:8080" network_mode: host volumes: - /:/rootfs:ro - /var/run:/var/run:ro - /sys:/sys:ro - /var/lib/docker/:/var/lib/docker:ro - /dev/disk/:/dev/disk:ro privileged: true restart: unless-stopped depends_on: - redis redis: image: redis:latest container_name: redis ports: - "6379:6379"

For CPU and memory metrics, you can use cAdvisor to collect container level data.

Perhaps https://github.com/google/cadvisor + prometheus (or influx or whatever else) + grafana?

We could have used a much more focussed tool like Prometheus or Cadvisor to gather system stats, but that is not the main objective of this article.

Result: Interestingly, the GitHub Issue that talks about cAdvisor and Docker Desktop for Mac for running cAdvisor is still open and not fixed.

If you're running things under systemd, you can enable process accounting and use cAdvisor.

Check this thread if you’re having difficulties, but it might run out of the box these days: https://github.com/google/cadvisor/issues/1846