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.

Comments

Using Fail2Ban to protect a Varnished site from scrapers

I'm using Varnish to cache a fairly busy property site. Varnish works like a bomb for normal users and has greatly improved our page load speed. For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site. I decided to use fail2ban to block IP's who hit the site too often. The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with. This means setting up varnishncsa. Add this to your /etc/rc.local file: varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log: /var/log/varnish/*log { create 640 http log compress ...

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred. The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change. Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal. One way to decouple your domain logic from both persistence and controller is to use the "repository pattern". Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...

Grokking PHP monolog context into Elastic

An indexed and searchable centralized log is one of those tools that once you've had it you'll wonder how you managed without it. I've experienced a couple of advantages to using a central log - debugging, monitoring performance, and catching unknown problems. Debugging Debugging becomes easier because instead of poking around grepping text logs on servers you're able to use a GUI to contrast and compare values between different time ranges. A ticket will often include sparse information about the problem and observed error, but if you know more or less when a problem occurred then you can check the logs of all your systems at that time. Problem behaviour in your application can occur as a result of the services you depend on. A database fault will produce errors in your application, for example. If you log your database errors and your application errors in the same central platform then it's much more convenient to compare behaviour between...

Adventures in IT

Search This Blog