Skip to main content

Zabbix open source monitoring

ZABBIX (visit http://www.zabbix.com) is an open source distributed monitoring solution for enterprise level applications. It is capable of providing detailed networking information as well as polling servers to establish their health.


ZABBIX was created by Alexei Vladishev, and currently is actively developed and
supported by ZABBIX SIA.


It is possible to configure ZABBIX to email alerts to the administrator for just about any event. This means that even if you have several servers to watch you will be able to react quickly to any arising problem.


ZABBIX code is released under the GPL2 license ( General Public License 2 ). It is free to use and requires no licensing fees. The ZABBIX company offers both free and commercial support options.


My company currently has 8 production servers, three of which host mission critical applications and databases. It is possible for one of our operations staff to remotely login to each machine, check the status of the applications, do a trace on the database, check the logs... do you see how time consuming this can be? Of course we're also assuming that the operations staff is willing to do this 24/7!


Today I'll be implementing this open source solution. Lets see how it goes :)


Update


I've now been using Zabbix for some time and have found it to be a generally positive experience. It does a good job of monitoring my servers, is fairly intuitive to set up, and has even landed our company a support contract. One thing that did bother me is that it insists on using a PHP function that the official PHP guide views as not being ready for production (see my later post here). I posted a question on the Zabbix forums and received no feedback from the community.



Oddly the most difficult part of getting Zabbix working was to reconfigure the rules on my firewall. I've inherited a messy set of rules, many of which apply to conditions that have ceased to exist within the company. Integrating new rules into this spaghetti requires concentration.



My next Zabbix challenge will be to implement the SMS send routines with a GSM modem. The documentation suggests that this should be easy as Zabbix natively supports SMS notification. Experience has shown me that very little promised in Linux documentation actually comes true. No doubt there will be a driver incompatibility, some software problem, or some other reason to make Zabbix misbehave.

Labels:

Comments

Post a Comment

Popular posts from this blog

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer.  Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted.  This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel.  A thorough comparison of the patterns is available  here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework.  It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database.  Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its glory in this demo.  
Post a Comment
Read more

Fixing puppet "Exiting; no certificate found and waitforcert is disabled" error

While debugging and setting up Puppet I am still running the agent and master from CLI in --no-daemonize mode.  I kept getting an error on my agent - ""Exiting; no certificate found and waitforcert is disabled". The fix was quite simple and a little embarrassing.  Firstly I forgot to run my puppet master with root privileges which meant that it was unable to write incoming certificate requests to disk.  That's the embarrassing part and after I looked at my shell prompt and noticed this issue fixing it was quite simple. Firstly I got the puppet ssl path by running the command   puppet agent --configprint ssldir Then I removed that directory so that my agent no longer had any certificates or requests. On my master side I cleaned the old certificate by running  puppet cert clean --all  (this would remove all my agent certificates but for now I have just the one so its quicker than tagging it). I started my agent up with the command  puppet agent --test   whi
Post a Comment
Read more

Redirecting non-www urls to www and http to https in Nginx web server

Image: Pixabay Although I'm currently playing with Elixir and its HTTP servers like Cowboy at the moment Nginx is still my go-to server for production PHP. If you haven't already swapped your web-server from Apache then you really should consider installing Nginx on a test server and running some stress tests on it.  I wrote about stress testing in my book on scaling PHP . Redirecting non-www traffic to www in nginx is best accomplished by using the "return" verb.  You could use a rewrite but the Nginx manual suggests that a return is better in the section on " Taxing Rewrites ". Server blocks are cheap in Nginx and I find it's simplest to have two redirects for the person who arrives on the non-secure non-canonical form of my link.  I wouldn't expect many people to reach this link because obviously every link that I create will be properly formatted so being redirected twice will only affect a small minority of people. Anyway, here's
Post a Comment
Read more