Our stand was located in the Cloud Computing Expo Japan section along with many other expert companies representing their latest developments in the related subject.

On the first day of exhibition several meetings with our Japanese partners took place. It was nice to finally meet them in person, as before we didn’t have such opportunity. We shared the experiences and made new plans to promote Zabbix in the Japanese market.

On the second day, Kodai Terashima, our Support Engineer gave a presentation on “Cloud Monitoring with Zabbix 2.0 OSS Monitoring Software” in one of the conference halls. We would like to thank everyone, who came to listen to Kodai, it is much appreciated. There were so many visitors that some of them had to stand yet this didn’t stop people from coming in

Today was the last day of Japan IT Week. We are still very excited, even though those have been 3 hard days of exhibiting. It is of course too early to speak about the results of the exhibition, but we may predict that in the very near future you will read about partnership agreements with new Japanese companies.

Thanks again to everyone who came to visit our stand and we hope you enjoyed yourselves at this event as much as we did!

Zabbix team joined other volunteers around Latvia to help the country become garbage-free. Together with family members Zabbixers spent this warm and sunny day tidying-up the territory of Biķernieku race track located just next door to our head office that also happens to be our favorite cycling place

Check out our pictures from that day and hopefully next time those of you who live in Latvia will join us for the Big Cleanup!

Starting  with 2.0.0rc3, all database upgrades for all supported databases will be fully supported.

This should be great news for those who would like to do extended testing, as it will allow to create more complex test data and keep it while upgrading. Additionally, this would be useful for people who would like to start with a test deployment, and are cautious about redoing all of their configuration for further 2.0.0 release candidates or the final 2.0.0 release.

This commitment is largely because of the Zabbix maintainer for Gentoo, MattM, who was asking for that on the Zabbix IRC channel

Current situation

Currently, Zabbix active agent can report to a single server only. There is just one process that works with active checks.

Multiple server support in 1.8.12 already

The chosen approach was simple enough to be implemented in Zabbix 1.8.12 already. From the user perspective, if they only want to use a single active server (or none at all), nothing changes. Note that agent doesn’t really know whether it is talking to a server or proxy, so multiple proxies or any combination of servers and proxies is supported as well. Everywhere further down when a “server” is mentioned, that also includes Zabbix proxies. Now, if a user wants to use more than one server for the active checks, things change a bit. First, there is a new configuration parameter – ServerActive. How it works:

• If ServerActive is specified, Server is not used for active checks, only for passive checks
• If ServerActive is not specified, Server is used same as before, that is, first host is used for active checks

If you were using the first host from the Server parameter for active checks and you add a ServerActive parameter, you must list the same host in the new parameter as well, otherwise it will be ignored for active checks. Of course, to achieve our goal of having multiple servers used, this parameter allows to specify multiple hosts here – comma separated. For example, it could list:

ServerActive=zabbixserver,zabbixproxy1,10.1.13.13

But what if a proxy on one of them is running on a non-standard port? Custom port can be specified for each host after a colon.

ServerActive=zabbixserver,zabbixproxy1:20051,10.1.13.13

Of course, IPv6 is supported as well… but wait, IPv6 addresses contain colons. How about specifying non-default port then? If IPv6 host must have port specified, IP address should be enclosed in square brackets (square brackets are optional if no port is used with IPv6) address, for example:

 ServerActive=zabbixproxy1:20051,[::1]:30051,::1,[::1]

For all hosts that don’t have a port specified here, port in ServerPort is used. If ServerPort is not specified, default port (10051) is used.

Different implementation in 2.0

The solution for 1.8 is great as it does not require any changes for users, upgrading to 1.8.12 or later from previous agent versions. It is not great as the behaviour is a bit cryptic and confusing – if this parameter is specified, we ignore something from that parameter, ports can be overridden in two ways… Given that 2.0 is a major upgrade it was decided to implement a simpler solution. A minor drawback is that some users will have to modify their agent daemon configuration files when upgrading agents to 2.0. So, 2.0 works exactly as 1.8 implementation, but with these differences:

• Hosts in the Server parameter are never used for active checks, only for passive checks – even if ServerActive is not specified
• ServerPort parameter is removed

Upgrading agent to Zabbix 2.0

For those users who are not using active checks, upgrade to 2.0 will not require any changes – unless they were specifying ServerPort (for some reason – it is not used for anything else besides active checks). For those users who moved to using ServerActive with 1.8, upgrade to 2.0 will not require any changes – unless they were specifying ServerPort.

• All users who used ServerPort will have to remove this parameter from their configuration files
• All users who used active checks in 1.8 without ServerActive parameter will have to add their server/proxy in ServerActive parameter. If they used ServerPort, that will also have to be added to corresponding hosts in the ServerActive parameter

How it works

Before this development, only one agent internal process was possible that would be responsible for active items. Now, for each host, specified in ServerActive, a new active item process will be created. Each process will work with one server only in an independent fashion. So these processes work totally in parallel, without any communication between them.

Item values are sent back to whichever server sent configuration data for them. If one server sends active item configuration data and another has no active items configured, only the first server will receive the values for those items. All the configuration data, received from servers, is handled separately by each internal process, so you should be careful with that – for example, if there is a script that should not be run in multiple copies simultaneously, you should never send item data from multiple servers that references this script. If you do, multiple active item processes will definitely attempt to run the script at the same time.

Error reporting

The new parameter syntax is a bit more complex than for the old Server parameter, so typos and other mistakes might be a bit more likely. Because of this (and because Zabbix becomes a bit more user-friendly lately ), error reporting should be fairly helpful. If Zabbix agent can’t parse some part of the addresses (there’s something totally wrong there), it will refuse to start up with a message error in ServerActive option at position <pos>, printing out the character position where the problematic content starts. If an address is specified twice in ServerActive, agent will refuse to start up with an additional message part address “host:port” specified more than once.

Where is it?

This functionality is available in 1.8.12rc1, and will be in the final release of 1.8.12. If you are interested in it, make sure to test 1.8.12rc1 as soon as possible.

Special thanks

Special thanks for help and support with this feature goes to:

• Takanori Suzuki for the initial idea and proof-of-concept patch
• Intelligence Business Solutions, Ltd. (Zabbix certified partner) for financing the complete development

Many leading Latvian companies were contributing to RTU Career Day and had their booths in the exhibition hall, too. Among them were the “SEB” and “DNB” banks, a leading telecommunications company – “Lattelecom”, Latvian Railway Company, the energy company – “Latvenergo”, the road construction company – “Latvijas ceļi”, IBM, Schneider Electric, Statoil, Draugiem.lv and many more.

It was a successful day for Zabbix at RTU Career Day. We met many bright students looking for a job or internship opportunities, we also met with representatives from a variety of Latvian companies and gave a presentation about Zabbix SIA and opportunities within it.

We would like to thank all the students who have passed the test and submitted their CVs on our website; we hope that some of them will become a future Zabbixer!

Here are some pictures from the event. Enjoy!

This post isn’t very timely, but there wasn’t much time for that on the third day of CeBIT, March 8th. Because it was by far the busiest day. We met some more old friends, talked to lots of new ones and showed off Zabbix. Questions about 2.0 were fairly common yesterday, so we did look at the current trunk version in practice a lot.

By the way, if you haven’t tried trunk version of Zabbix yet, make sure to do so – you can check it out from our svn server and compile.

Monitoring-FR : Results in 2011 for Zabbix: objectives achieved? What are your main satisfactions and disappointments?

Alexei Vladishev : I am happy to say that 2011 was another successful year for Zabbix.
It was the most successful year in terms of growth rate as well as absolute revenue numbers so far. We moved to a new bigger office, our core team grew to 22 people working full time on Zabbix. Also our World presence was extended thanks to our new partners.

The main disappointment, if we may call it this way, of the last year is the fact that Zabbix 2.0 is still not released. It is a result of our old wrong approach of “let’s add a bunch of new features and fix all those bugs later on”. The schema does not work.

Early last year we switched to a new development procedure allowing us to keep trunk, the latest code, as stable as possible. Let’s see how it works, but I’m sure it is already bringing
positive changes and will allow us to release new versions in the expected time frame.
I have to admit that more and more large companies use Zabbix. Quality, stability and ease of maintenance become crucial.

Last year we made serious effort of improving QA, created continuous integration platform, new development procedures, created and published coding standards and other things in order to be confident in the quality of our product. We are making very good progress in constant delivery of a better quality. Zabbix users notice these positive changes for sure.

It is interesting that some brave people already use pre-2.0 (in beta state currently) in production and I can understand why. New version has so many improvements that it’s really hard to resist. Indeed, quality of the server, proxy and agents is impressive in the latest betas, front-end deserves more testing though. Despite of this I do not recommend beta versions for production systems. Please be patient and wait for the official release of 2.0.

M-fr : Within the community Monitoring-fr, we found a rather interesting increase in the number of users of Zabbix. How do you stand in relation to competition in the French market in 2011?

Alexei : I do not think we are competing with other open source solutions. I believe market of open source monitoring solutions is still growing. We help each other actually in this respect.

Also I feel that we are in more direct competition with proprietary solutions rather than with open source alternatives. Part of our philosophy is that we do not fight for customers by any means. Those who quickly make decisions about the use of a solution may quickly change their mind if it is not too late of course. For me it’s important that the choice is based on honest comparison of technical and business benefits.

Someone on the forums called Zabbix a product for smart people. That’s very important to me. One should spend some time in order to understand the flexible architecture of Zabbix and the way Zabbix is designed to work. However as soon as you get the understanding, you won’t be disappointed by its functionality and high flexibility. Do not make your choice based on current popularity, it may change quickly. Make your chance based on your own evaluation of competing product for your unique requirements.

Let’s talk about France. Actually, France is in Top 5 countries of visitors to the Zabbix home page this year. It’s quite unexpected result of breaking into the Top 5, taking into account that this top is quite strongly held by a group of countries, traditionally being the most active adopters of Zabbix, i.e. USA, Japan, Russia and Brazil.

Currently Zabbix is used by several large French companies, including two leading banks which work with us quite actively. By the way, a couple of weeks ago we opened a new forum in French. Feel free to come and share your experience at www.zabbix.com/forum !

M-fr : Nagios is important in France. In addition, the French solution named Shinken seems to grow up with, among other things, its ease of migration (Nagios to Shinken). What are your plans to impose Zabbix on the Open Source monitoring market in France?

Alexei : There are no specific plans about France, but we treat it very seriously. I am sure you may expect much more visibility of Zabbix in France after the release of Zabbix 2.0.
Having local community contributes to a project a lot. I urge our French friends to be more active in spreading word about Zabbix.

M-fr : Given the historical weight of using Nagios in France, and the natural tendency to move towards a Shinken (see Centreon). Now, how are you convince users to select and then to migrate to Zabbix?

A.V. : Nagios has huge inertia in the minds on the people. However, we may still notice absolutely new projects based on Nagios. I think it’s easy to explain. It’s much easier to create a better Nagios based on Nagios, rather than come up with unique ideas. Obviously, Nagios is a good enough foundation for the creation of new products.

Let me explain some good points of our solution.

Zabbix was created from the scratch. It has no dependencies of other tools with the only exception of low level libraries such as net-snmp lib. Everything apart of WEB front-end is written in C language, which gives us massive advantage in speed and much lower hardware requirements. The whole Zabbix core is just a binary of 2MB in size. Even for large setups having more than 10K of devices to monitor it rarely needs more than 2GB of memory (not including requirements for the database.)

Upgrading from one minor version to another is just a matter of installing new binaries. For major upgrades the back-end database has to be updated as well. All configuration and historical data is kept in a relational database, which makes maintenance straight forward.

Zabbix API allows nice integration with other systems, such as configuration management, incident management, and other monitoring systems.
Monitoring of remote locations, branch offices or client sites has never been an issue for Zabbix thanks to Zabbix Proxy. Zabbix Proxy is a light-weight daemon collecting performance and availability data from remote networks. It supports both push and pull modes making it a perfect choice for those looking for high performance monitoring of sites behind firewalls or in DMZ. Proxy is immune to communication problems due
to support of data buffering. Zabbix Agents support buffering as well.

Zabbix provides native agents for nearly all platforms available around, including Linux, Windows, AIX, HP-UX, Solaris, Tru64 and various BSD systems. The agent is a 1-2MB binary with no external dependencies, able to process tens of thousands of requests per second if you ever need this level of performance. It executes native system calls only, no Perl, Python, Java on client side! Backward compatibility of agents is maintained for all versions of Zabbix starting from the very first release of Zabbix 1.0.

If you may get any data out of your devices, be absolutely confident Zabbix will be able to monitor it, graph it and alert you in case of any issues. This level of flexibility makes it great.

M-fr : Soon Zabbix 2.0? Some additional information? Announcements ?

Alexei : I have to disappoint you if you ask for an exact release date. Zabbix 2.0 will be ready when it is ready, but we are very very close. At the moment we are finishing XML import/export, which is the only missing functionality of 2.0. Also we have few blocker issues in our bug tracking system to fix. First release candidate will be out when all this is done. I expect a few RCs prior to official 2.0 giving our users chance to try it before the official release.
Do not expect revolutionary changes. Zabbix 2.0 will be another step in right direction. That’s how we are developing out product. It’s important to deliver better product with every new release instead of surprising users with sudden huge modifications. However architecture should be also reviewed when needed.

M-fr : New features in 2.0 are very promising, including the network’s discovery of low-level and improved use of the inventory. There is also a new customizable interface (graphics, maps, …). Zabbix 2.0 will hit hard, isn’t it ?

Alexei : No doubts, we are delivering massive improvements in 2.0. Let’s have a look at the most interesting features of 2.0.

It would be possible to monitor remotely Java applications using JMX without need of Zapcat, SSL could be optionally used for extra security. Zabbix 2.0 introduces low level discovery (LLD), it delivers automatic discovery of devices, disk volumes, network interfaces, etc. It is not about the discovery of network devices, it is all about the discovery of
resources on the device level. It allows to greatly decrease the number of templates used, make them simpler and even more flexible.

Dynamically changed configuration is no longer a headache for Zabbix administrators thanks to this new feature. You may get much more detailed information about LLD by reading Zabbix Manual at http://www.zabbix.com/documentation/2.0/manual/discovery/low_level_discovery Good thing about LLD is that it can be easily extended by implementing custom discovery of any objects that you would like to monitor.
Zabbix 2.0 offers much higher level of performance thanks to in-memory caching of trigger-related information, it decreases the load on the database and lowers the hardware requirements. Here we continue our good tradition of delivering better performance with every new Zabbix release.

I have to mention changes related to the Zabbix front-end. It became easier to use, especially when it comes to configuration and administration. In addition to that we introduced a new shiny set of map icons for nearly all types of devices. Maps also support displaying of group of hosts not as a single icon, but as individual icons for all of the hosts. Now new devices will automatically be displayed, no need to add them manually.

Another important improvement is ability to use standard localization framework based on GNU gettext. We have Zabbix front-end translated to many languages including, of course!, French. Translators could make translation in a much more efficient way! Anyone is welcome to participate.
Now you can restart (boot, shutdown) servers and securely execute any commands on Zabbix agents side straight from the front-end.

We have screens based on templates. Now host related information could be grouped in a set of host-level screens.

Zabbix Agent supports more metrics for different platforms. Note that there is no need to upgrade existing 1.x agents in order to migrate to 2.0. Zabbix agents are backwards compatible.

Historical data got nano-second resolution. Visible host names were introduced to give hosts more meaningful naming based on your naming conventions in any language. Items support description field. Scope of use of user macros was significantly extended. They could be used in SNMP parameters as well as for security related information (user name, password) for SSH and Telnet checks, for example.

Another significant improvement is automatic collection of inventory data, which may gather any information that an agent can return, which in turn allows to extend this by any command.

Pro-active monitoring has also been improved. Zabbix now is able to execute remote agent/SSH/telnet-based commands for automatic resolution of discovered problems. That’s a great feature, which is normally used as a part of escalation process.

WEB monitoring was extended so that Proxy is able to execute WEB scenarios. Now it is possible to monitor performance and availability of your web application from different geographical locations, say, Japan, USA and Europe, simultaneously.

Other features?

Zabbix 2.0 brings lots of new features and minor improvements. Most of them are described in good detail on this page: http://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew200
Some of initially planned functionality was not included into 2.0. It’s sad that flexible configuration of dashboard was postponed to 2.2.

M-fr : Recently, you offer a Commercial license version of Zabbix. Are there any technical differences with the GLPv2 version? Can you say more to our community?

Alexei : Let me explain. Zabbix has always been true free software without any strings attached, we continue following our philosophy of making free software. In the same time we build our business model on delivering commercial services such as yearly support agreements, training programs and sponsored development.

GPL licence is quite strict when it comes to integration of GPL code in other products or use of the code in commercial context. In order to avoid these limitations we offer commercial licensing for companies, interested in tight integration of Zabbix or its use in proprietary products. It has nothing to do with closed or open-core model. Zabbix has always been, is and will be fully free software with excellent commercial support.

I have to admit that it’s not easy to build a company and develop free software. All we do is based on selling our services. Our future depends on support of our customers. I’m still trying to find the best business model.

M-fr : Are you planning one day to attend an event in France ? Such as for example the “Salon des Solutions Linux” in Paris?

Alexei : I will be happy to participate in a conference to talk about Zabbix, my experience and topics related to free and open source software. Feel free to invite me – just drop me an email, there is a great chance I’ll come. Please be aware that I do not speak French.

M-fr : Zabbix SIA will be present at CeBIT 2012 in Germany. What are your expectations of this event? Your ambitions?

Alexei : I think that the main reason of being on CeBIT is to deliver a message to our potential partners that we are ready for expansion in the German market. Germany has great potential to become an important market for our product. We are well known, however not enough. We will demonstrate new functionality of Zabbix 2.0 and of course it is an opportunity for all interested to talk to me and my colleagues. Come visit us!

M-fr : What are the objectives of this year 2012?

Alexei : Release of Zabbix 2.0 is our primary target to be done very soon. Then we’ll be working on finalizing roadmap for 2.2 and do the actual development work, which would take most of our resources until the end of this year. The roadmap will be published on our web site as soon as it is ready.

We are going to carefully review the list of suggested functionality, most popular features have all chances to be included into 2.2. Stay in touch with the latest news!
As announced during the Zabbix Conference last year, we are moving to a fixed 9-month release cycle just after the release of Zabbix 2.0. It basically means that we may expect Zabbix 2.2, next major version, in early 2013.

I think that work on a better front-end is one of the major priorities for the future. When I say better, I mean user interface which is friendly, easy to understand, with great navigation and customizable.

Large Zabbix installations collect massive amounts of historical data, look after tens of thousands of devices and may generate hundreds or even thousands of events per second. Zabbix has all the information about performance and availability available, the front-end must be good enough to represent it in the most useful way. Current Zabbix front-end is not perfect in this sense. I am dreaming about implementing a zero-bug policy, it would allow us to dramatically improve the way we work with reported issues and bug fixing.

By the way, do not miss your chance to visit Zabbix Conference 2012 in September this year. I am sure all the participants were very excited about the conference last year, and I am sure this year it will be even better and full of surprises.

See you, and keep in touch by subscribing to our Twitter channel #zabbix.

The second day was even more busy than before, this is a small snapshot of people flocking towards the fairground:

Zabbix team also visited the open source park in hall 2 – nice to see some presence in CeBIT.

Of course, the ever-vigilant Tux was present there as well:

Meanwhile, back in hall 6, Latvian corner is active and fun:

With the first day being so busy, we didn’t have the time to fully present all the goodies we had – but we did so on the second day. If you haven’t done so yet, swing by our corner and get a few stickers, including the fairly-recent “Monitored by Zabbix” ones

Oh, just a quick reminder: we’re in hall 6. For those with visual memory:

CeBIT, one of the biggest trade shows in the world, has happened since 1986. With the first day, March 6, progressing nicely, Zabbix has arrived and settled there as well.

Zabbix is located in Hall 6 inside the Latvian stand – D08 (it’s close to the restaurant in this hall). Have any interest in Zabbix – or even open source in general? Come visit us (we have candy).

A more integrated experience for virtual environment monitoring is currently being considered for development. It might cover VMware, Xen, KVM (and possibly other environments), and include easy-to-set-up monitoring of both hypervisor and guest virtual machine statistics.

A common approach today is to monitor guest virtual machines using Zabbix agent in each of them. This does not cover virtualisation-specific metrics, and does not include hypervisor level monitoring, which has to be set up using extra functionality like external checks, user parameters or Zabbix sender. It works rather nicely, but doesn’t feel that native to Zabbix – and in larger environments there might be performance gains in a native solution as well.

Currently considered functionality includes:

• Support for VMware, Xen and KVM
• Monitoring hypervisor and guest virtual machine status using hypervisor API
• Management of the guest virtual machines from the Zabbix frontend

But to make this functionality powerful and easy to use some backing would be needed. Do you know a company that might be interested in partially financing an integrated virtual environment support? Let us know.

There already are several interested parties, and if there are enough of them, such development could be scheduled for Zabbix 2.2 already. A (partial) list of benefits sponsoring company would get:

• Close involvement in the specification drafting process
• Notifications of development progress
• Access to early development versions for testing
• Feedback being taken into serious consideration
• Co-marketing opportunities

Are you interested? Contact us (either by sending e-mail to sales /at/ zabbix /dot/ com or filling out the contact form) and we’ll let some more details of our grand plan slip.

(Japanese translation of this post)