Zabbix Documentation 1.8

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


Sidebar

jp:manual:about

Table of Contents

1 概要

20.1 Zabbixの概要

20.1.1 Zabbixとは?

ZabbixはAlexei Vladishevによって作成され、現在はZabbix SIAが積極的に開発およびサポートを行っています。

Zabbixはエンタープライズに対応した監視ソリューションであり、オープンソースで配布されています。

Zabbixは多数のネットワークやサーバの稼働状態と整合性監視するためのソフトウェアです。Zabbixは柔軟性の高い通知メカニズムを備え、ユーザはあらゆるイベントからメールベースの通知を行うように設定することができます。これらの機能によりサーバの障害に迅速に対応することができます。Zabbixは保存されたデータをもとにすぐれたレポートやデータのグラフィカル表示機能を提供します。これらの機能により、キャパシティプランニングに最適です。

Zabbixはポーリングとトラッピングの両方をサポートします。Zabbixの全てのレポート、統計情報、および設定パラメータはWebベースのインターフェースからアクセスできます。Webベースのインターフェースはどのような場所からでもアクセスでき、ネットワークやサーバの稼働状態を確認することができます。適切に設定することで、ITインフラストラクチャを監視する重要なツールとしてZabbixを活用することができます。少数のサーバを有する小規模な組織から、大量のサーバを有する大企業まで同じように利用できます。

Zabbixは無料です。ZabbixはGPL(General Public License)バージョン2の下で作成および配布されています。ソースコードは無料で配布され、誰でも自由に利用できます。

Zabbix SIAが提供する商用サポートを利用することも可能です。

20.1.2 Zabbixの機能

Zabbixは以下の機能を提供します:

  • サーバおよびネットワークデバイスのオートディスカバリ
  • 中央のウェブ管理インタフェースからの分散監視
  • ポーリングとトラッピングのサポート
  • サーバソフトウェアはLinux、Solaris、HP-UX、AIX、FreeBSD、OpenBSD、OS Xに対応
  • ハイパフォーマンスな専用エージェント(クライアントソフトウェアはLinux、Solaris、HP-UX、AIX、FreeBSD、OpenBSD、OS X、Tru64/OSF1、Windows NT 4.0、Windows 2000、Windows 2003、Windows XP、Windows Vistaに対応)
  • エージェントレス監視
  • セキュリティで保護されたユーザ認証
  • 柔軟なユーザパーミッション管理
  • ウェブインタフェース
  • 事前定義されたイベントをメールベースの柔軟なアラート機能で通知
  • 監視対象リソースのハイレベル(ビジネス向け)な表示機能
  • 監査ログ

20.1.3 Zabbixの特長

  • オープンソースソリューション
  • UNIXベースとWIN32ベースのプラットフォームに対応した高性能エージェント
  • インタフェースが直観的ですぐに習熟できる
  • 高いROI(ダウンタイムは非常に高コストのため)
  • 所有コストが低い
  • 設定が単純でわかりやすい
  • 集中化された監視システム(設定やパフォーマンスデータなど全ての情報をリレーショナルデータベースに格納)
  • 高度なサービスツリー
  • 簡単にセットアップ可能
  • SNMP (v1,v2)のサポートトラッピングとポーリングの双方をサポート
  • 監視データをグラフィカルに表示
  • 設定により古いデータを削除

20.1.4 Zabbixユーザ

世界中のあらゆる規模の企業や組織が、メイン監視プラットフォームとしてZabbixを採用しています。

2010/07/05 04:47

20.2 目標と原則

20.2.1 Zabbixの開発における主な目標

Zabbixは、以下の目標を設定しています。

  • オープンソースの監視ソフトウェアとして認識されるようになること
  • Zabbixユーザグループを創設し、ZABBIXのさらなる改良に努めること
  • 高品質な有料サポートを提供すること

20.2.2 Zabbixの開発における主な原則

  • ユーザの使い勝手を重視すること
  • 何事も単純化すること
  • 処理に使用するリソースをできるだけ少なくすること
  • 迅速に対応すること
  • ソフトウェアのあらゆる側面をドキュメント化すること
2010/07/05 05:05

20.3 インストールとアップグレードに関する注意事項

20.3.1 インストール

詳細はソースからのインストールを参照してください。

20.3.2 バージョンの互換性

Zabbix1.0、Zabbix1.1.x、Zabbix1.4.xとZabbix1.6.xの古いエージェントをZabbix1.8で使用することができます。エージェント側で設定を変更する必要はありません。

古いバージョン1.6.xのZabbixプロキシはZabbix1.8で使用することはできません、アップグレードする必要があります。

20.3.3 重要な注意事項

20.3.3.1 For version 1.8
  • All hosts now are required to belong to at least one group.
  • CPU index for system.cpu.util key on Linux now starts with 0.
  • Key vfs.fs.size returns data in bytes for all operating systems now.
  • Key vfs.fs.size now takes into account reserved diskspace for root user.
  • Comment at the end of a configuration file line is not allowed anymore (this worked for numeric parameters only before).
20.3.3.2 For version 1.8.3
  • Parameter service.ntp for item keys net.tcp.service and net.tcp.service.perf renamed to ntp. Old syntax is still supported.
  • Trying to run IPv6-enabled daemon on a system without IPv6 support fail:
    Listener failed with error: socket() for [[(null)]:10051] failed with error 97: Address family not supported by protocol.
20.3.3.3 For version 1.8.5
  • The method of external command invocation for Zabbix daemons has been changed to allow terminating runaway processes. Instead of using standard popen method as before, Zabbix now explicitly calls /bin/sh to execute desired command.
  • Trying to run a Zabbix daemon, compiled on Linux kernel 2.6.27 or later on a system with kernel 2.6.26 or older will fail:
    socket() for [[-]:10050] failed with error 22: Invalid argument
20.3.3.4 For version 1.8.6
  • Zabbix daemons now refuse to start up if configuration file contains incorrect parameters. If old parameters have accumulated in the configuration files, this will result in inoperable daemons after the upgrade until the parameters are fixed.
20.3.3.5 For version 1.8.8
  • In some cases hosts and proxies with identical name might have appeared in the Zabbix database. In 1.8.8, Zabbix server will shut down if it detects such a situation. This check was removed in 1.8.9.
20.3.3.6 For version 1.8.9
  • The shutdown upon detection of duplicate hosts, introduced in 1.8.8, has been removed.
20.3.3.7 For version 1.8.16
  • Accepted data limit of 128MB was introduced when using Zabbix protocol. Any other data (including older Zabbix protocols) stays limited at 16MB.

20.3.4 システム要件の変更

システム要件の追加または変更:

  • サポート対象からPHP4を除外
  • PHPの最大メモリサイズは、少なくとも128MB (memory_limitオプション)
  • PHPの最大POSTサイズは、少なくとも16MB (post_max_sizeオプション)

また、1.8.21.8.3 および1.8.9の要件の変更を参照してください。

20.3.5 既知の問題

1.8のZabbixのフロントエンドではSQLiteを使用できません。サポートされている他のデータベースを使用してください。
20.3.5.1 For version 1.8
  • PHP mbstring check may fail with PHP < 5.2 in Zabbix 1.8. To avoid this issue, copy zabbix.conf.php.example file to zabbix.conf.php and modify parameters, including database access parameters.
  • For IPMI support you need a recent OpenIPMI version - 2.0.14 and later is known to work.
  • Sorting in frontend is not performed for entities with positional variables (like item names with $1 etc).
  • XML export includes SNMP and other information for all items.
  • Hostnames with spaces do not work when sending data from a file with zabbix_sender (fixed in 1.8.2).
  • Uploading of images for network maps may fail if database is not configured properly. Make sure database, tables and fields are set to UTF-8 encoding.
  • Precompiled binaries (agent, sender, get) might not work on 64bit systems with glibc versions older than 2.5. Common symptom is failing to start with the error message: Floating point exception. Use older versions, or compile from the scratch on the target system.
20.3.5.2 For version 1.8.2

Because of frontend changes, some installations might see incorrect older data appear in frontend. These include:

  • Incorrect trigger appearing, with name **ERROR**, usually in Monitoring → Triggers section, when showing all hosts from all groups. This trigger can be deleted by clicking on it, choosing Configuration of triggers, then clicking on Delete in the trigger editing form and confirming the deletion.
You might have to remove groupid=&hostid=& part from the URL when attempting to delete the trigger.
  • Depending on the installation time of your Zabbix server, default graphs might have incorrect configuration. This only affects you if those graphs are being used. Opening such a graph usually will swap working time and trigger showing with percentile values. If that is the case, simply fixing and saving the graph will solve the problem.

20.3.6 アップグレード手順

Zabbixの1.6.xのから1.8に正常にアップグレードするために次の手順を実行する必要があります。 Zabbixのデータベースのサイズによってアップグレード手順に数時間かかることがあります。

20.3.6.1 Zabbixサーバ停止

データベースにデータが追加されないようにするためにZabbixサーバを停止します。

20.3.6.2 既存のZabbixデータベースのバックアップ

これは非常に重要なステップです。データベースのバックアップがあることを確認します。アップグレード手順が失敗(ディスク容量の不足、電源オフ、予期しない問題)した場合、バックアップから復旧します。

20.3.6.3 設定ファイル、PHPファイルとZabbixバイナリのバックアップ

Zabbixバイナリ、設定ファイルとPHPファイルをコピーしバックアップを作成します。

20.3.6.4 新しいZabbixサーバ(バイナリ)のインストール

コンパイル済みバイナリを使用するか、自分でコンパイルしてください。

20.3.6.5 サーバ設定パラメータの確認

zabbix_server.conf一部のパラメータが1.8で変更されました。あなたはそれらを確認することができます。

  • Zabbixサーバとプロクシ設定ファイルからStartDBSyncersオプションは削除されました。
20.3.6.6 データベースのアップグレード
1.6から1.8などのメジャーなZabbixバージョンをアップグレードする場合、データベースのアップグレードは必須のステップです。 特にリリースノートに明記しない限り、1.8.xからは1.8.xのようなマイナーバージョンのアップグレードにはデータベースのアップグレードは必要ありません。

アップグレード·スクリプトを実行する前に、以下のインデックスをdrop:

MySQL

alter table dhosts drop index dhosts_1;
alter table dservices drop index dservices_1;
alter table httptest drop index httptest_2;
alter table httptest drop index httptest_3;
alter table history_log drop index history_log_2;
alter table history_text drop index history_text_2;
alter table actions drop index actions_1;
alter table escalations drop index escalations_2;
alter table graphs_items drop index graphs_items_1;
alter table graphs_items drop index graphs_items_2;
alter table services drop index services_1; 

Oracle or PostgreSQL

drop index dhosts_1;
drop index dservices_1;
drop index httptest_2;
drop index httptest_3;
drop index history_log_2;
drop index history_text_2;
drop index actions_1;
drop index escalations_2;
drop index graphs_items_1;
drop index graphs_items_2;
drop index services_1; 

存在しないインデックスに関する警告メッセージは無視します!

データベースのアップグレードスクリプトは、ディレクトリ upgrades/dbpatches/1.8/<db engine> に配置されています:

  • MySQL: upgrades/dbpatches/1.8/mysql/patch.sql
  • Oracle: upgrades/dbpatches/1.8/oracle/patch.sql
  • PostgreSQL: upgrades/dbpatches/1.8/postgresql/patch.sql

データベースのアップグレードは10〜15分程度かかりますが、PostgreSQLは履歴データの変換に数時間以上かかることがあります。本番環境以外でのアップグレード手順をテストすることをお勧めします。

UTF-8にデータベースを変換する場合、時間がかかることがあります。

十分な権限(テーブルの作成/削除、インデックスの作成/削除)を持っていることを確認してください。また、ディスクに十分な空き領域があることを確認してください。

これらのスクリプトは、Zabbixの1.6.xのからわずか1.8へのアップグレードのためです!(Zabbixの1.6.x)以前のバージョンからのアップグレードの場合、Zabbixの1.6.x.にアップグレードするスクリプトも使用します。

20.3.6.7 新しいZabbix GUIのインストール

インストール手順に従ってください。

20.3.6.8 新しいZabbixの起動

新しいバイナリを起動します。バイナリが正常に開始しているかどうかを確認するためにログファイルをチェックします。

2013/08/12 09:45

4 What's new in Zabbix 1.8

More than a year in making, Zabbix 1.8 has arrived with lots of new features, as well as improved old ones. You can introduce yourself to the changes for this new version of Zabbix in the following section.

21 Notable improvements

With so many changes it is impossible to pick 3 most notable ones - which is attempted below. For this reason, it is suggested to read on, as some generally minor feature might be very important to you.

22 New features and improvements for the frontend

Zabbix web frontend is the feature that sets it apart from other solutions. Powerful, yet easy to use official GUI is shipped with the default package. It provides both non-intimidating access for novice users and large scale configuration features for sizable installations.

Being most user-visible part, we will start by looking at many new features and improvements in Zabbix 1.8 for the web frontend.

22.1 Bar reports

Zabbix already has easy to use simple graphs that do not require any configuration - these are provided for every numeric item. Custom graphs, along with a couple simplistic reports, allow to look at the data in context. Zabbix 1.8 brings much more powerful built-in reporting.

New report category, bar reports, allows to look at the data from many different angles. Want to look at the weekly temperatures in the server room for the last two months? Have to compare webserver load for the first month of every quarter this year? All that and more is possible with this new feature.

22.2 Full Unicode support

While previous Zabbix versions were multi-language friendly, providing several frontend translations, it was not a truly global thing - the most popular encoding, Unicode, was not fully supported.

Zabbix 1.8 now fully supports Unicode/UTF-8, allowing for a true localised or multilanguage setup.

22.3 Improved time period navigation

In Zabbix, single control is used to select time period displayed for many views, including simple and custom graphs, raw data, screens and web monitoring. Already improved in 1.6, time period selector has been improved in 1.8 further.

This scrollbar allows easy dragging and resizing of it. Additionally, links on the left hand side allow to choose some predefined, often used time periods and move displayed period forward/backward in time. And the dates on the right hand side actually work as links, popping up a calendar and allowing to set specific start/end time.

Notice the dynamic/fixed link in the lower right hand corner? It can be used to control whether time period is kept constant when you change start/end time.

In addition to the screenshots you can also view the video of using graph time period controls.

22.4 Improved graphs

Zabbix graphs have been improved in many ways. This includes both visual and functional improvements, like the time period selector already mentioned. For example, information about max/min/avg values is presented clearly as a table.

22.4.1 Improved timeline in charts

Zabbix graphs - or charts - usually display time on x axis. And even this representation has been improved in the new version.

Comparing 1.6 and 1.8:

Axis labels in 1.6.
Axis labels in trunk.

As can be seen, labels are now easier to read. Instead of prioritising some arbitrary point in time, depending on graph scale, actual points in time like change of a day are prioritised. Sometimes Zabbix will even use more “human readable” labels:

22.4.2 Gradient line support in graphs

Zabbix graphs support several line styles, and 1.8 brings one more - gradient line. It's easier to understand how that works by looking at an actual example.

22.4.3 DejaVu font used for graphs

DejaVu font is now used for graphs for nice looking text - and for Unicode capabilities.

22.5 Improved map editing

Zabbix supports network maps where monitored environment can be laid out on a background image to provide user friendly overview.

In previous versions, editing such network maps was not easy - coordinates of each element on the map had to be specified manually.

Map editing in Zabbix 1.8 has been greatly improved by adding drag and drop support, as well as selected element detail displaying in a popup.

You can even watch a video of map editing.

In addition to that map links may have optional text for displaying arbitrary information, for example, bandwidth data.

Background map CC-BY-SA Openstreetmap.

22.6 Changed configuration layout

Zabbix web frontend provides convenient way to display and visualise received data, as well as configure all aspects of monitoring.

Layout of this configuration has been redone in 1.8. Instead of separate sections for items, graphs, triggers and so on, they are folded into host configuration section, where convenient linking allows for easy access to all of these entities and more.

On the other hand, host group configuration has been brought out on the configuration menu.

Another change is general configuration being moved to administration section to avoid Zabbix administrator level users from having access to global configuration parameters.

22.7 Visual trigger editing frontend

Usage thresholds and any other problem conditions are freely configurable by user. These definitions are called triggers, and complex expressions can be used for each trigger to define what is considered a problem.

In addition to ability to edit trigger expressions directly, a frontend to create triggers visually has been added.

There is a special mode for creating log related triggers.

It also incorporates ability to provide test data and try out trigger behaviour.

(screenshot)

22.8 New and improved filters

As Zabbix frontend provides means to access all the information, it can be a daunting task to find the desired one. Previous versions offered ways to filter this information, and 1.8 improves situation in this regard by adding new filters and making existing ones more powerful.

22.8.1 Items filter

Item configuration section is the one where all aspects regarding data gathering are configured, thus it is displaying quite a lot of information. Being able to quickly find desired data gathering entries is crucial to efficient configuration, and in Zabbix 1.8 there's an improved filter for items that allows for much more detailed searching.

(screenshot)

After performing initial filtering, subfilter becomes available. It presents found values and results can be filtered further.

22.8.2 Audit filter

Accountability is important on any system with more than one user (and on many systems with single user as well). Zabbix frontend records all operations in an audit log.

In version 1.8 audit logs now can be filtered quite extensively to find exactly the changes you are looking for.

22.8.3 Latest data filter

Looking at shiny graphs is tempting, but sometimes you need the real data. Latest data section in Zabbix frontend allows to see exact values for all monitored metrics.

It is now possible to filter this screen by freeform search against item descriptions.

22.8.4 Reworked "Status of triggers" view

Trigger view is widely used to display list of current problems, and it was possible to display recent events for all the problems, limited by day count.

In 1.8, this screen gained has been changed, providing new features like expanding individual triggers to show their events and confirming all events for a trigger.

22.8.5 Other filters improved

Filters in other sections of the frontend have been improved as well, allowing to get to the data easier and more quickly.

22.9 Improved screen editing

Zabbix screens is a feature that allows to group many frontend elements, including graphs, network maps, raw data and many others. Configuring them initially was not very hard, but making any significant changes was nearly impossible in some cases.

Screen editing has been greatly improved in 1.8. This includes:

  • Drag and drop support. Dragging an element to empty cell will move it there, dragging an element on occupied cell will switch these elements. You can watch a video of this feature (site also allows to download original .ogg video).
  • Using icons on the screen edges, rows now can be inserted and removed from arbitrary locations.

There's now a search box in the upper right corner, which allows searching in hosts, host groups and templates.

Results allow for a quick access to found entities and their elements:

22.11 Minor frontend improvements

For a GUI minor visual change can bring large benefits to the user. Zabbix 1.8 has many minor improvements and features that should make working more productive and pleasant.

22.11.1 Cleaner error displaying

Error messages are now shown as icons and error text is available in a popup. Clicking the icon opens the popup to allow copying of the message.

22.11.2 History strings saved by reference

At the top of the frontend, there's a breadcrumbs type history, showing recently accessed pages.

When a language is switched in frontend, in previous versions existing history entries would not switch language, only new entries would be added in the correct language. Now history strings change appropriately.

22.11.3 Paging for entity lists added

Many locations of Zabbix frontend present information as lists - whether it's a list of hosts, items or triggers. These lists can get quite long on large installations of Zabbix, and that slows down frontend considerably.

Zabbix 1.8 supports splitting long lists in multiple pages. Entry count per page is configurable in user's profile.

Configuring rows per page in user profile
Entry limit in action
22.11.4 Selected rows are highlighted now

Most of the entries in these lists can be selected for performing some operation on them.

A minor but welcome improvement in 1.8 - selected rows now are hilighted.

22.11.5 Ability to display server name

Setting variable ZBX_SERVER_NAME allows Zabbix server name to be displayed in the frontend upper right corner.

It is also used in page title.

22.11.6 More flexible linked items

Zabbix supports very powerful templating that makes large scale configuration management easy. Templates can be linked to monitored hosts and they determine what and how is monitored.

Downstream linked items in Zabbix 1.8 are more flexible now - for example, it is possible to edit SNMP parameters like community string, or allowed hosts for trapper items, in items that are linked in from templates.

22.11.7 IP address becomes default option

In host creation form, IP address is now the default choice.

22.11.8 Debug mode added for frontend

Mostly useful for developers, but can be handy when trying to determine source of a problem for others as well.

Debug mode can be enabled on user group basis.

22.11.9 Help icons lead to online manual

Oldtime Zabbix users might remember the days when help icons from Zabbix frontend linked to the online manual. With the conversion to online documentation that again is possible, and in Zabbix 1.8 most of these icons open Zabbix manual in a new browser window or tab.

23 API

In version 1.8 first, Zabbix provides JSON-RPC API. It already allows to perform most of the configuration changes, thus enabling powerful means for automated or complex setup management.

While API itself might not be that exciting for casual users, it enables creation of various tools. One such tool already has been created - Zabbix commandline utility or Zabcon.

Zabcon is especially exciting for users who would like to perform uncommon, large scale changes, as it allows easy scripting without programming skills.

Zabbix management from servers without GUI installed also is expected to be possible, and surely users will come up with innovative and impressing uses for this tool.

Note: API is currently considered to be in a technical preview state and can change in next versions.

24 Improvements for larger installations

Zabbix is being used in larger and larger environments every day. 1.8 release introduces several changes that are specifically useful in average and above setups.

24.1 Performance improvements

When monitoring hundreds and thousands of devices, load on the monitoring server hardware can become a serious issue. Zabbix 1.8 brings many different improvements to the performance in several key areas.

24.1.1 Increased Zabbix server and proxy performance

Doing the main work behind the scenes, Zabbix server has been improved greatly to allow gathering more data on the same hardware. As Zabbix proxy shares some code with the server, it has benefited from these changes as well.

24.1.1.1 Much more efficient polling

Hundreds of pollers can be executed for greater parallelism and performance. The pollers do not communicate directly with the database and use very little of server CPU and memory resources.

24.1.1.2 Added configuration data cache module

Database cache is enabled by default and can not be disabled. Configuration option StartDBSyncers has been removed from Zabbix server and proxy configuration files.

A special internal check has been introduced, zabbix[wcache,*] to monitor health of this cache.

24.1.2 Frontend images recompressed with pngcrush

To reduce amount of data that users have to retrieve from webserver when using Zabbix frontend, all PNG images have been recompressed for optimal size.

24.1.3 Items with SNMP dynamic index use one connection

Zabbix supports monitoring SNMP metrics that have dynamic identifiers.

In version 1.8 index resolving and data retrieval is performed in a single connection now, reducing network load and load on the monitored devices.

24.2 Automated host management improvements

For larger or constantly changing environments replicating these changes in Zabbix configuration can be a challenge. Zabbix already supported network discovery, and 1.8 now brings both improvements to the network discovery, as well as new methods to automate adding of new devices to monitor.

24.2.1 Network discovery improvements

Network discovery, available in previous versions, has received multiple improvements.

24.2.1.1 Port interval support

For services where it's appropriate, port interval support has been added.

24.2.1.2 New action operations

Based on discovery events, two new operations have been added, thus increasing available operation count for network discovery to 10.

  • Enable host
  • Disable host

24.2.1.3 IP mask support

Industry standard network mask notation can now be used in network discovery, for example, 192.168.1.0/24.

24.2.1.4 Support for multihomed devices

If a host provides some service on multiple IP addresses, it would be discovered as multiple hosts in Zabbix versions before 1.8. Starting with 1.8, it is possible to use different uniqueness criteria for some services, for example system.uname returned by Zabbix agent or any OID returned by SNMP capable host.

24.2.1.5 SNMPv3 support

Network discovery in Zabbix 1.8 supports SNMPv3 with all the corresponding functionality.

24.2.2 Auto registration for active agents

Completely new in Zabbix 1.8, it is possible to allow active Zabbix agent auto-registration, after which server can start monitoring them. This allows to add new hosts for monitoring without any manual server configuration for each individual host.

The feature might be very handy for automatic monitoring of new Cloud nodes. As soon as you have a new node in the Cloud Zabbix will automatically start collection of performance and availability data of the host.

24.3 Support for global, template and host level macros

Support for user definable macros (or variables) has been added. These can be defined globally for Zabbix installation, on template and host level. For example, defining the following macros on a host level allows to set custom thresholds per host, even if all hosts are linked against single template:

In this case, templated trigger expression would be:

{ca_001:system.cpu.load[,avg1].min({$CPULOAD_PERIOD})}>{$MAX_CPULOAD}

25 Various

25.1 Host maintenance

Host and host group maintenance has been added to Zabbix.

Hosts that are in maintenance are indicated as such in Monitoring → Triggers view.

If a problem happens during the maintenance and is not resolved, notification is generated after maintenance period ends.

If a log item is added while host is in maintenance and maintenance ends, only new logfile entries since the end of the maintenance will be gathered.

25.2 Improved audit log

Zabbix provides accontability by recording all user logins and changes to the Zabbix configuration in the audit log.

Audit log in 1.8 has been improved, and instead of simply seeing that something has changed, many entities will have exact changes recorded.

Exact changes made to item preserved
Exact changes made to trigger preserved

25.3 New macros

Zabbix provides very useful variables - called macros - to be used in item names, notifications and elsewhere. Zabbix 1.8 increases the amount of available macros, as well as making some macros usable in more locations.

25.3.1 In notifications

Along with existing macros new ones can be used in notifications that are sent out.

  • {NODE.*[1..9]}
  • {ITEM.LOG.*[1..9]}
  • {ITEM.VALUE} and {ITEM.VALUE[1..9]}
  • {ITEM.LASTVALUE[1..9]}
  • {HOST.CONN[1..9]} {HOST.DNS[1..9]} {IPADDRESS[1..9]}
  • {TRIGGER.KEY[1..9]}
  • {HOSTNAME[1..9]}
  • {ITEM.NAME[1..9]}
  • {PROFILE.*[1..9]}
  • {EVENT.ACK.STATUS}
  • {EVENT.ACK.HISTORY}
  • {TRIGGER.EVENTS.UNACK}
25.3.2 In map labels

Map labels allow using handy macros like the current value of some item.

  • {TRIGGERS.UNACK}

25.4 Advanced regular expression editor

Advanced regular expression editor was added to Zabbix with ability to test regular expressions. It is now possible to define complex regular expression with easy to use interface and reuse them with simple reference.

25.5 IPv6 support for SNMP monitoring

In addition to the SNMP related improvements for network discovery, IPv6 support has been implemented for SNMP monitoring.

25.6 Supported PHP version changes

Zabbix frontend is based on PHP. Since the last stable Zabbix release there have been major changes in PHP versions, and Zabbix frontend has been changed accordingly.

25.6.1 Support for PHP 5.3 added

Released in 2009.06.30, PHP 5.3.0 was out for some time to require support of Zabbix frontend.

25.6.2 Support for PHP 4 dropped

Last bugfix release in 2008.01.03 and last release with security fixes in 2008.08.07, PHP4 was not receiving bugfixes anymore.

Zabbix 1.8 requires PHP 5.0 or later.

26 Minor improvements

We call these minor, but for somebody one of these might be the biggest change in Zabbix 1.8.

26.1 Basic authentication support in web monitoring

Web monitoring now supports basic HTTP authentication. It can be configured per scenario.

26.2 New and improved monitored metrics

While Zabbix can be extended, built-in checks require less resources and are easier to use. Zabbix 1.8 introduces several new checks and improves old ones.

26.2.1 New items

Several completely new items have appeared.

  • icmppingloss
  • net.tcp.dns.query
26.2.1.1 CPU switches support on Linux

Key system.cpu.switches can be used for Linux hosts.

26.2.1.2 Added Windows services key

Added services key for Windows which can return services in a particular state.

26.2.2 ICMP items have new parameters

Zabbix ICMP items now are much more flexible. Item icmpping has gained the following parameters:

  • target - host IP or DNS name;
  • count - number of packets;
  • interval - time between successive packets in milliseconds;
  • size - packet size in bytes;
  • timeout - timeout in milliseconds.

Now it is possible to use a key like this:

icmpping[10.10.10.10,5,300,128,100]

This would send five 128 byte packets to host with IP 10.10.10.10 with 300 ms interval between them, and use 100 ms timeout.

Item icmppingsec has gained all the above parameters, and one additional:

  • mode - one of min, max, avg.

Default mode is avg.

26.2.3 'maxlines' parameter for log items

Item keys log and eventlog now have new parameter - maxlines. It specifies maximum number of new lines per second the agent will send to Zabbix server or Proxy.

By default, Zabbix agent does not send more than 100 log lines per second per log file. For fast growing file the number can be increased using the new parameter.

26.2.4 New Windows eventlog filters

Windows eventlog entries now can be filtered by type, source and event ID on the agent side.

26.2.5 SSH and telnet checks

Now SSH and telnet can be used for direct, agent-less monitoring. SSH supports both password and key authentication methods.

It makes possible very effective remote monitoring of network devices, appliances and servers without use of Zabbix Agent.

Currently SSH and telnet cannot be used in actions, this functionality will be available in future releases.

26.2.6 LVM swap devices support

LVM devices are now supported as swap devices on Linux.

26.2.7 First CPU number changed on Linux

First CPU on Linux is now referred to as 0, which is consistent with other operating systems.

26.2.8 Positive sign for decimal values supported

If incoming decimal (float) value is preceded by a + sign, it is supported as a positive number now.

26.3 New input data types

While different base values could be monitored before with user parameters, that was not easy enough. Zabbix 1.8 natively supports two new input data types, sometimes found on devices like printers.

  • Octal
  • Hexadecimal

26.4 Client utilities moved to bin

Zabbix client utilities zabbix_get and zabbix_sender were moved from sbin to bin.

26.5 Improved sample configuration files

Sample configuration file layout was changed. Now all parameters are included, and their default values, as well as allowed ranges, are documented.

26.6 Added manpages

Manpages for all Zabbix processes have been added.

26.7 Notification media can be chosen in action operations

It means that it's possible to define messages that will be sent to one or several media only. For example, all critical messages can be delivered by using SMS messaging, while other messages using both email and SMS without creating multiple actions.

26.8 Timestamp support for zabbix_sender

Support for -T parameter in zabbix_sender has been added, which allows to set timestamp for each value. The option can be used to migrate older historical data from other monitoring tools to Zabbix database for graphing and long-term analysis.

26.9 Manual user unblocking

Ability to manually unblock users who have been locked out by bruteforce protection was added.

Clicking on the Blocked link will unblock this user.

26.10 Native support of Oracle

Previous version of Zabbix had a dependency on a third party library called sqlora8. The library is not actively developed any more. Oracle support is now implemented using native Oracle Call Interface, which greatly improves performance and stability of Zabbix setups using Oracle as a back-end database.

26.11 Host status propagation from proxies

If a host is monitored by a proxy, status of the host will be correctly displayed and updated in Zabbix front-end.

26.12 Rotated logfile monitoring

Zabbix supports logfile monitoring, and version 1.8 improves it further. If an application is writing to a new logfile with varying name - for example, if logfile name includes date - it is much easier to monitor with Zabbix 1.8, as it is now possible to specify regular expressions in logfile monitoring.

26.13 Online documentation

Documentation from an inflexible PDF file has been converted to online format where anybody can comment on individual pages. Offline documentation can still be obtained with ODT export functionality.

26.14 Detailed availability information displaying

Instead of simply displaying generic host status, in 1.8 frontend three different monitoring methods have their status displayed - Zabbix agent, SNMP and IPMI.

Errors related to each method are stored separately and can be obtained by moving mouse cursor over the error icon.

Default theme uses green to denote availability, while Black&blue theme uses blue colour.

What's new in further releases

See detailed information on new features and significant changes in other 1.8 series releases:

Installation and upgrade

See the installation section for new installations.

See upgrading section if upgrading from an older Zabbix release.

Before upgrading, read important notes.

2009/09/26 09:53