Zabbix introduction, zabbix
Zabbix is an enterprise-level open-source solution that provides distributed system monitoring and network monitoring functions based on the WEB interface.
Zabbix consists of zabbix-server and zabbix-agent. The supported monitoring protocols include ICMP, IPMI, SNMP, HTTP, and zabbix (the most commonly used protocol is used to monitor various monitored terminals ).
The collected data is stored in the database. The database supports mysql, oracle, and so on.
Third Component: zabbix web gui interface provides web pages to monitor and manage the monitored terminals.
Fourth Component: zabbix proxy (non-essential component for implementing distributed monitoring, with more than one thousand of monitored servers .)
Workflow:
Zabbix_get collects data from the client. zabbix_agentd listens to a socket to receive zabbix_get requests and sends the data collected and sent to the server through zabbix_sender. The data is stored in the zabbix database for testing, write scripts or execute commands remotely.
The zabbix server automatically periodically collects data from the monitored end and determines which data is collected by the server in advance.
Zabbix server, zabbix database, and zabbix web gui can be deployed on one server. To improve performance, they can be deployed on different hosts.
Common zabbix terms:
Host: the network device to be monitored, which can be specified by the IP address or DNS name.
Host group: the logical container of the host, which can contain hosts and templates. However, the hosts and templates in the same group cannot be linked to each other; generally, a host group can be used when users or user groups are assigned a monitoring permission ).
Item.
Trigger: the trigger is beyond the defined range. This guy will trigger an alarm.
Event: all events are generated by triggers.
Action: how to deal with events, such as what operations to perform.
Escalation (ALARM escalation): if the system does not respond within the defined 5 minutes, it will be upgraded from the warning level to the high Level to remind others to handle it as soon as possible.
Media: the means and channels for sending alarms, such as Email.
Remote command: a predefined command that can be automatically executed when the monitored host is under a specific condition.
Template: it is used to quickly define a set of Preset entries for the monitored host, including item, trigger, graph, screen, application, and low-level discovery rule; the template can be directly linked to a single host. (It doesn't matter if you don't understand this concept, as long as you know how to operate it)
Application: a set of items.
The relationship between the above terms can be expressed (just a general understanding ):
This process is to obtain data from each client.
The data generated by zabbix is mainly composed of four parts:
Configuration data (ignore)
Historical data: 50 bytes
Historical Trend data: 128 bytes
Incident Data: 130 bytes
Through the calculation of the above data, we can determine the size of zabbix database we need to customize disk hardware.