When monitoring Windows servers and services it would be really handy to have a check to see if all the services that are registered with the system to automatically start up during boot, are also started.
EPEL finally offers Zabbix 2.0 packages. These packages are for you, if you are running RHEL, CentOS, Scientific Linux or any other Red Hat derivative. EPEL aims to provide best quality packages, that follow the same rules and conventions as Red Hat packages and therefore integrate smoothly.
To be known, accepted and demanded in the different corners of the world is of course a big honor and the pride of every developing and dynamic company. However, to become recognized by the company’s home country and to be named “the best”, that’s what makes you really proud of who you are and what you are doing, as we all know – the most honest critique and valuation of the things you do comes from the closest people. 🙂
On October 31st we introduced to our truly beloved Facebook followers an autumn contest, called “Zabbix Explorer”. During one month, until November 28th, the most enthusiastic, nimble, persistent and passionate Zabbix fans were competing with each other in order to win the title of ”Zabbix Explorer 2012”! 🙂
The 2.0.4 release contains a lot of improvements so one tiny change may have passed unnoticed: the version of the API has been bumped to 2.0.4 as well. Indeed, that’s one small change in the code, but a huge decision for the Zabbix developers team. The API version has remained on 1.4 since the release of 2.0, but finally we’ve developed a versioning that will suite our needs.
The Zabbix API is a great tool, which allows you to extend and tailor Zabbix to your specific needs. Yet using it still poses a challenge for many developers, because a lot of it is still undocumented. To solve this problem and make the API more open to third party developers we’ve decided to completely rewrite the documentation. Yes, everything. From scratch.
JMX monitoring with Zabbix is easy using Zabbix Java gateway. Let’s say you have a JMX-enabled Java application running on some host. You start the Java gateway, configure Zabbix server to use that, add that host in Zabbix frontend, set up a JMX interface and create a JMX agent item (described here). A JMX item key name is (surprise-surprise!) jmx and it needs 2 parameters that describe a monitored entity: