Zabbix Architecture Introduction

First, ZABBIX basic structure

Second, Zabbix common terms

Three, Zabbix logical structure diagram

First, ZABBIX basic structure

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/6E/22/wKiom1V0VrizYCrhAAR8zzvcfTI972.jpg "width=" 1021 "height=" 619 "/>

Server1:zabbix server, ZABBIX_AGENTD or zabbix_proxy collect data to be saved to Server3

Server2: Based on the Apache PHP platform combined with Zabbix Web GUI, this component accesses the Zabbix Administration page via a browser-connected web GUI

Server3: Database server, providing data storage capabilities

Zabbix_sender:agentd send data to Zabbix server when the exception occurs

Zabbix_get: Communication with AGENTD, pull data actively

ZABBIX_AGENTD: Can monitor database,device,application

Zabbix Proxy: In a distributed environment, all monitored devices communicate with them, collect data from them, and send them to Zabbix server regularly, reducing the amount of server concurrency

Second, Zabbix common terms

Host: The network device to monitor, which can be specified by IP or DNS name

Host group: Logical container for hosts, including host and configuration templates

Monitoring item: The data of a particular monitoring indicator, which is derived from the monitored object

Trigger (Trigger): An expression that evaluates whether the data for the monitor object is in a reasonable range, that is, the threshold, and when the data is greater than the threshold, the trigger state is converted from "OK" to "problem", and when the amount of data is returned to a reasonable extent, its state will be from "problem" Convert to "OK"

Event: A noteworthy thing that occurs, such as a change in the state of a trigger, the automatic registration of a new agent or a re-launched agent, and so on

Action: A pre-defined processing method for a specific event, including the condition (when the action is taken) and the action (such as sending a notification)

Alarm escalation (escalation): A custom scheme that sends an alert or executes a remote command, such as sending an alert every 5 minutes, sending a total of 5 times, etc.

Medium (Media): a means or channel for sending comrades, such as e-mail,sms,jabber, etc.

Notification (notification): To send information about an event to a user via the selected media

Remote command: A predefined command that can be executed automatically when the monitored host is under a certain condition

Template: A set of preset entries that are used to quickly define a monitored host, usually containing item, trigger, graph, screen, application, and low-level discovery rule, Templates can be linked directly to a single host

Application (Application): Collection of a set of item

Web Scene (Web Scennario): One or more HTTP requests to detect Web site availability

Front End (frontend): Zabbix Web Interface

Three, Zabbix logical structure diagram

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/6e/22/wkiom1v0vrjwryn3aaglesnr8mi765.jpg "width=" 873 "height=" 625 "/>

Zabbix poller: Zabbix Server,zabbix poller based on pull mechanism pull data via SNMP protocol, Zabbix Agent, Internal, etc.

Zabbix Agent: Collect the item data of the monitored device, and perform (actions) pre-defined processing methods such as sending e-mail or other actions by monitoring the threshold-trigger (triggers) state for such event (events)

Host: Depending on the environment, there may be more than one host (hostgroups)

This article is from the "Arvin Lau" blog, be sure to keep this source http://64314491.blog.51cto.com/2784219/1659497

Zabbix Architecture Introduction