The process of Zabbix (1)

Version: 3.4

First, the process

1) Server

Zabbix server is the core program for the entire Zabbix software. The Zabbix server process runs as a daemon (deamon).

2) Agent

Zabbix agent is deployed on the target of monitoring and proactively monitors local resources and applications (Hardware drivers, memory, processor statistics, etc.).

Passive (passive) and active (active) checks

Zabbix agents can perform both passive and active inspection methods.

In passive check mode, the agent answers the data request, Zabbix server (or proxy) asks the agent data, such as the load on the CPU, and then Zabbix the agent to echo the results.

The Active checks processing process will be relatively complex. The agent must first request a list of monitoring items from Zabbix sever for independent processing, and then periodically send new values to the server.

Performing a passive or active check is configured by selecting the appropriate monitoring project type. Item type. Zabbix Agent processing monitoring item types are ' Zabbix agent ' and ' Zabbix agent (Active) '.

3) Proxy

Zabbix Proxy is a process that collects monitoring data from one or more monitored devices and sends the information to Zabbix Sever, which basically represents Sever's work. All collected data is cached locally and then routed to the Zabbix sever to which the proxy belongs.

Deploying proxies is optional, but can be very useful for dispersing the load of a single Zabbix sever. If only proxy collects data, the process on the sever will reduce CPU consumption and disk I/O load.

Zabbix Proxy is the ideal solution for centralized monitoring of remote areas, branch offices, and networks that do not have local administrators.

Zabbix proxy requires the use of a separate database.

Zabbix Proxy database can be used with SQLite, MySQL, PostgreSQL. There are certain risks and limitations when using Oracle or IBM DB2 databases (e.g., return values in low-level discovery rules) return to the values of low-level discovery rules.

The Zabbix proxy runs as a daemon.

Process user

Zabbix Proxy is designed under a non-root account. It will run in the same way as any other non-root user-initiated process. Therefore, you can run the agent with any non-root user without any problems.

If you are running under the ' root ' account, it will switch to a hard-coded "Zabbix" user who must exist on your system. If you only want to run the proxy as ' root ', you must modify the ' allowroot ' parameter in the proxy quota file.

4) Java Gateway

Overview

Starting with the Zabbix 2.0 release, the native support monitoring JMX program in the form of the Zabbix daemon appears, which is known as the Zabbix Java gateway. Zabbix Gateway is written in the Java language. To find a host-specific JMX counter value, Zabbix server sends a request to Zabbix Java Gateway, which uses the JMX management API to request a remote application. The app does not require additional software to install, it only needs to be specified at the command line at startup -Dcom.sun.management.jmxremote .

The Java gateway accepts incoming connections from the Zabbix server or agent and can only be used as a passive proxy. In contrast to Zabbix proxy, it can also be called from the Zabbix agent (the Zabbix agent cannot be linked). Each Java gateway access is configured directly in the Zabbix sever or proxy configuration file, so only one Java gateway can be configured per Zabbix sever or Zabbix agent. If a master implements JMX agent type of monitoring item and other types of monitoring items, only the JMX agent monitoring items are passed to the Java Gateway for retrieval.

When a monitoring item value on the Java gateway is updated, the Zabbix server or agent will connect to the Java gateway to request the value, and the Java Gateway will retrieves back to the server or proxy in turn. Similarly, Java Gateway does not cache any values.

Zabbix Sever or proxy has a process that connects to a specific type of Java gateway, controlled by the start_pollers option. Internally, the Java gateway initiates multiple threads that are controlled by this option. On the sever side, if the connection exceeds Timeout seconds, it will be terminated, but the Java gateway may still be busy retrieving values from the JMX counters. To solve this problem, the Zabbix 2.0.15,zabbix 2.2.10 and Zabbix 2.4.5 have a timeout option in Java Gateway that allows setting timeouts for JMX network operations.

The Zabbix server or agent will centralize requests to a single JMX target (affected by the monitored item interval) and send them to the Java gateway in the same connection for better performance. It is recommended that startjavapollers is less than or equal to start_pollers, otherwise it may cause Java gateway to have no extra threads to handle when connecting to the Java gateway

The following details describe how to get and run Zabbix Java Gateway, how to configure Zabbix server (or proxy) to complete JMX monitoring with Zabbix Java Gateway, and how to configure the monitoring items in the Zabbix GUI, To match a special jmx counter.

4.1 Getting the Java Gateway

There are two ways to get Java gateway, one is to download the Java Gateway package via the Zabbix website, and the other is to compile the Java gateway through the source code.

4.1.1 via Zabbix website

Zabbix Java Gateway Package (RHEL, Debian, Ubuntu) can be downloaded from http://www.zabbix.com/download.php.

4.1.2 Compiled by source code

In order to compile the Java gateway, you need to add the –enable-java option when you run the./configure. We recommend that you specify the –PREFIX option at installation instead of using the default/usr/local because the entire directory tree is created when you install Java gateway, not a single executable file

$./configure--enable-java--prefix= $PREFIX

Use make to complete the Java Gateway Compilation and package it into a jar file. It is important to note that this step will require javac and jars, so you need to ensure that they are in the path

$ make

You will now get the zabbix-java-gateway-$VERSION. jar file under Src/zabbix_java/bin. If you are satisfied with using Java gateway under the specified directory, you can complete the configuration and run the Java gateway, otherwise make sure you have sufficient permissions to run made install.

$ make Install


5) Command line application
Sender, Get

The process of Zabbix (1)