It's been a long time since I worked on the monitoring plugin check_win_net_usage.sh, a plugin to measure (and mainly graph) network I/O on Windows hosts.
But since November I am (again) integrating Windows hosts into an Icinga2 monitoring solution. The recent modifications in November weren't big changes to the plugin itself, however the newest addition is worth a little post about it.
With today's version (20151215) the plugin supports an automatic discovery of network interfaces on the target Windows host. This was always the most difficult part to figure out the correct name of the interface to monitor, because Windows sometimes named the interfaces differently in the OS as presented to the logged in user.
Here's an example how to use the new detection with the -d parameter:
./check_win_net_usage.sh -H 10.10.10.50 -p 1248 -d
vmxnet3 Ethernet Adapter _5
This interface name can then be used with the -i parameter to start monitoring:
./check_win_net_usage.sh -H 10.10.10.50 -p 1248 -i "vmxnet3 Ethernet Adapter _5"
Network OK - 16542 Bytes received/sec, 11120 Bytes sent/sec|bytes_in=16542B;;;; bytes_out=11120B;;;;
This should help a lot of users who have struggled to find the correct interface name.
I also adapted the documentation of check_win_net_usage to not only cover example configurations for Nagios and Icinga 1.x but also for Icinga 2 - including an apply rule.
No comments yet.
Personal Internet VMware PHP Linux Shell Bluecoat Proxy Windows Hardware Virtualization Nagios MySQL DB Monitoring Mail Android Network Wyse Hacks Tomcat Postgres Apple Mac Backup BSD ZFS Solaris SmartOS Unix Multimedia Perl Database MongoDB CMS OTRS FreeBSD Wordpress LXC Nginx Proxmox DNS Graphics GlusterFS Security Chef HAProxy Icinga Ansible HTML MariaDB Containers Rancher Docker AWS ELK Kibana Logstash Filebeat Varnish PGSQL PostgreSQL ElasticSearch CouchDB Bash Macintosh Container Minio Grafana InfluxDB Databases NFS OSSEC SystemD Java Zoneminder Surveillance Elasticsearch SSL TLS Icingaweb2 Cloud Wireless Kubernetes Ubuntu