Zabbix 3.0 Released: What's New

Here it is! The expected and desired Zabbix 3.0 is here with the fount of new features. Let’s skim them over and put them in practice.

Redesigned WEB interface

The frontend in 3.0 comes with a more modern design, being now more convenient and easier to use. The UI is now cleaner with some usability improvements, for example, Users section has been split into User groups and Users. Plus, all the minor adjustments, like the change in font face and size, lead to a more lightweight and user-friendly frontend.

Daemon communication encryption and authentication

Encryption of traffic between all Zabbix components (server, proxies, agents and command-line utilities) protects from intercepting of data.

Encryption also provides authentication – only components with trusted certificate or pre-shared key can take part in communication. The authentication is mutual - e.g. not only Zabbix server examines agent's certificate but the agent also can be configured to examine server's certificate issuer and subject.

Encryption is optional and configurable for individual components (e.g. some proxies and agents can be configured to use encrypted communications with server while others can use unencrypted communications as before).
Users uninterested in encryption can use Zabbix as before. However their Zabbix installations will be upgraded to be ready to support encryption. They can start using encryption gradually at any time.
There is no need to open new ports on firewalls – encrypted and unencrypted connections share the same ports.

Forecasting and trend prediction

Problem prediction long before they occur – in Zabbix 3.0 this will turn into reality.

Some say, that even in 2016 disks are still filling up… To prevent applications suffering from free disk space shortage, Zabbix can predict when this situation is going to happen and warn in advance. So that one can add more disk space just in time before it really becomes an issue and causes any damage.
Future behavior of the monitored system will be determined based on the historic data. Plus, you can choose appropriate interval and forecast horizon.

Per-process CPU utilization monitoring

With a new item called “proc.cpu.util” available on Linux and Solaris platforms, now it is possible to monitor CPU utilization of a specified process or a group of processes.

Performance improvements

History cache optimization

There was an issue of the speed of processing cached data. History cache worked fast when the stored items / values ratio was high. But the lower the stored items / values ratio was, the more history slots must have been iterated to pick the values for processing.
Now the history cache internal structure is redesigned. When a small set of items is flooding server with values, history syncers will process the cached data in short order.
History index cache was added to keep index of the history cache. A new zabbix[wcache,index,] internal check was added to monitor history index cache usage.

Action caching

In 3.0, actions and action condition will be stored in configuration cache and no longer be queried from the database. This is done in order to ease the work with big installations and a grand amount of actions and events.

Ready for business checks: execution of an item at a specific time

Previously, if you needed to check something once a day you were not able to specify an hour or minute of the check. The check could be performed at night or in the afternoon and you were not able to control that. Now you can schedule time intervals of item execution yourself.

Private maps, screens and slide shows

Now Zabbix supports private maps, screens and slide shows with the ability to share with other users and user groups. The functionality enables creation and management of maps, screens and slide shows for regular users without admin rights.

Support for multiple escalator processes

Escalator process of Zabbix server is responsible for processing actions. On large installations the number of actions can be big and single escalator process might be not able to handle the load. This may result in notifications being sent with the latency. Since 3.0 it is possible to specify more than one escalator process to be run.

Linking to applications based on discovery values

To help with logical grouping of items created from item prototypes by low-level discovery (LLD), it is now possible to assign the discovered items to application that are based on the values of LLD macros. There is now an option for creating application prototypes in item prototype definition.

Forced housekeeper execution

The housekeeper process of Zabbix server is responsible for deleting old data from the database. If there is a lot to delete, it may require a lot of system resources. This might negatively affect other Zabbix processes that are performing more important tasks.

Since 3.0 it is possible to disable automatic housekeeper procedures and execute it and Zabbix proxy. Automatic housekeeping procedures can be disabled in configuration file:

Running Zabbix daemons in foreground

Zabbix daemons now run in foreground accepting –f (--foreground) command line option. To redirect Zabbix logs to standard output when running in foreground set LogType configuration parameter to console.

Among other advantages this functionality allows easy dockerizing of Zabbix components.

Dependencies between trigger prototypes

Trigger dependencies have been part of Zabbix for quite a while. If you are monitoring a host that is behind a router, you don't want to receive an alert about the host if the router goes down.

But this feature was not available for trigger prototypes. Not until 3.0. In 3.0 you are able to do it. This allows you, for example, to have triggers with different thresholds (e. g. warning, emergency) for discovered disk devices when monitoring their free space.

Windows service discovery

In order to have a direct method to check if a certain service is running properly and not to log in on a server to find out the names of services on a host, the new low-level discovery item “service.discovery” is introduced.

It allows now to explore Windows services automatically and use prototypes to define items and triggers for each service’s state. Services of interests can be filtered using regexp discovery filters.

SMTP authentication support

Previously, Zabbix server could only send email alerts by connecting to a hardcoded port 25 of the specified SMTP server and sending an email without encryption or authentication. Now it will be possible to point out the encryption and authentication when configuring e-mail alerts.

Exporting and importing value maps

Value mappings can now be imported and exported separately. Furthermore, hosts and templates are exported together with the configured value mappings. Also when importing value mappings, there is an option to create new and update existing value mappings from XML.

A lot more

But this is not all as there are more than 50 new features to explore!

For more info or details, take a look at the official Zabbix What's New page or contact