Hi all,
VmBix 2.2 was released.
VmBix is a multi-thread TCP server written in java, it accepts connections from a Zabbix server/proxy/agent or zabbix_get and translates them to VMWare API calls.
Starting from version 2.2, Zabbix can natively monitor a VMWare environment. But there are a few drawbacks :
•The monitored items are not all very relevant.
•The created ESX and VM hosts are mostly read-only. You cannot attach them different templates or monitor them with an agent.
VmBix helps you to overcome this limitations, with very good performance. It is multi-threaded and can be queried using a Zabbix loadable module. VmBix also exposes VMWare API methods that are not always included in Zabbix, for example the Performance Counters.
Thanks to kireevco, RPM & DEB packages are now automatically created for VmBix (https://github.com/dav3860/vmbix) and its Zabbix loadable module (https://github.com/dav3860/vmbix_zabbix_module). There is also a breaking change : for the perf counter methods the rollup type must be added a the end of the query. See the CHANGELOG below :
- BREAKING CHANGE : Refactored the performance counter methods to include the rollup type in the counter name. Instead of querying a performance counter like this for example :
It now has be be queried like this :
The *.counter.list and *.counter.discovery methods have been updated in the same way.
- The project now uses Travis-CI and Bintray to automate the building and distribute the packages.
- Packages for Debian/Ubuntu and RedHat/Centos are automatically created. You can get them here.
- A new method vm.discovery.full[*] was added. It returns a JSON array of VMs including their power state, if you need to filter the LLD rule on the power state of the VMs.
- The methods cluster.cpu[name,usage] and cluster.mem[name,free] had issues. They have been fixed.
The packages for the loadable module are here.
VmBix 2.2 was released.
VmBix is a multi-thread TCP server written in java, it accepts connections from a Zabbix server/proxy/agent or zabbix_get and translates them to VMWare API calls.
Starting from version 2.2, Zabbix can natively monitor a VMWare environment. But there are a few drawbacks :
•The monitored items are not all very relevant.
•The created ESX and VM hosts are mostly read-only. You cannot attach them different templates or monitor them with an agent.
VmBix helps you to overcome this limitations, with very good performance. It is multi-threaded and can be queried using a Zabbix loadable module. VmBix also exposes VMWare API methods that are not always included in Zabbix, for example the Performance Counters.
Thanks to kireevco, RPM & DEB packages are now automatically created for VmBix (https://github.com/dav3860/vmbix) and its Zabbix loadable module (https://github.com/dav3860/vmbix_zabbix_module). There is also a breaking change : for the perf counter methods the rollup type must be added a the end of the query. See the CHANGELOG below :
- BREAKING CHANGE : Refactored the performance counter methods to include the rollup type in the counter name. Instead of querying a performance counter like this for example :
Code:
zabbix_get -s localhost -p 12050 -k vm.counter[VM01,cpu.usagemhz]
Code:
zabbix_get -s localhost -p 12050 -k vm.counter[VM01,cpu.usagemhz.average]
- The project now uses Travis-CI and Bintray to automate the building and distribute the packages.
- Packages for Debian/Ubuntu and RedHat/Centos are automatically created. You can get them here.
- A new method vm.discovery.full[*] was added. It returns a JSON array of VMs including their power state, if you need to filter the LLD rule on the power state of the VMs.
- The methods cluster.cpu[name,usage] and cluster.mem[name,free] had issues. They have been fixed.
The packages for the loadable module are here.
Comment