Example code for configuring monitoring items and aggregated graphics in Zabbix

1. Install Zabbix Agent to monitor the local machine

Install the agent software

Unlike the server, the Agent only needs to install the zabbix-agent package

cat /etc/yum.repos.d/zabbix.repo 
[zabbix]
name=Zabbix Official Repository - $basearch
baseurl=https://mirrors.aliyun.com/zabbix/zabbix/3.4/rhel/7/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
 
[zabbix-non-supported]
name=Zabbix Official Repository non-supported - $basearch
baseurl=https://mirrors.aliyun.com/zabbix/non-supported/rhel/7/$basearch/
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX
gpgcheck=1

curl https://mirrors.aliyun.com/zabbix/RPM-GPG-KEY-ZABBIX-A14FE591 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
curl https://mirrors.aliyun.com/zabbix/RPM-GPG-KEY-ZABBIX -o /etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX

yum -y install zabbix-agent zabbix-get

2. Configure the Agent and start it

vim /etc/zabbix/zabbix_agentd.conf
Server=39.108.140.0 # Passive mode zabbix-server-ip
ServerActive=39.108.140.0 # Active mode zabbix-server-ip
Hostname=You-Men # The host name of the Agent, which is the name that is finally displayed on the monitoring page UnsafeUserParameters=1 # Whether to restrict user-defined keys from using special characters systemctl restart zabbix-agent
netstat -antp|grep agent
tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN 3898/zabbix_agentd 
tcp6 0 0 :::10050 :::* LISTEN 3898/zabbix_agentd

3. Configure snmp (optional)

In addition to using agent to obtain data, zabbix can also obtain data through snmp. In order to enable zabbix to monitor more information, start the snmp function of the local machine.

yum -y install net-snmp net-snmp-utils
vim /etc/snmp/snmpd.conf
com2sec notConfigUser 39.108.140.0 public
access notConfigGroup "" any noauth exact all none none
view all included .1 80
systemctl restart snmpd && systemctl enable snmpd
ss -anup |grep snmp # 161 port, udp protocol # Test whether the snmp protocol works normally # snmpwalk -v 1 -c public 39.108.140.0 .1.3.6
# Use version v1, with the community public, to walk the .1.3.6 branch of 192.168.0.1.

snmpwalk -v 2c -c public 39.108.140.0
# Use the v2c version, set the community to public, and walk 39.108.140.0.
# -v displays the current SNMPWALK command line version.
# -
# Get the interface type of the cisco device 39.108.140.0

Next, we go to the web interface to configure how to monitor the local host. We see that the interface is 127.0.0.1, but our configuration file says 39.108.140.0. Let's make these two IPs consistent. Click 3 to enter and modify.

After the update, jump to the page below, wait for a while, and reload the page. The availability will be green.

At this point, monitoring the local host is complete. If you want to monitor the network card traffic of the local host, follow the steps in Figure 2 below. Click the numbers one by one with the mouse. If you want the monitoring items to be in Chinese, you can do Zabbix fault example 1. However, version 4.4 has been improved compared to previous versions. The monitoring items are not garbled, but in English.

If you want to change this garbled code into normal Chinese

If it is Windows, search for simkai.tff Chinese Kaiti in the C drive, copy/upload it to the server, and then cp it to the font directory of Zabbix 3.* version:
cp /root/simkai.ttf /usr/share/zabbix/fonts/

# Different installation methods will have different paths, so you can directly find / -type d -type fonts to find a similar folder, that's it # Pay attention to font permission issues vim /usr/share/zabbix/include/defines.inc.php
 define('ZBX_GRAPH_FONT_NAME', 'simkai');
 define('ZBX_FONT_NAME', 'simkai'); 

4. Zabbix monitors remote hosts

If zabbix-agent cannot be installed on the remote host, the package can be transferred through the machine where zabbix-agent is installed.

yum -y install yum-utils
# Download to the specified directory yum install zabbix-agent -y --downloadonly --downloaddir=/root
1. Install zabbix agent
 # Method 1 (the foreign source zabbix seems unable to download the package, use the above source):
 # rpm -Uvh https://repo.zabbix.com/zabbix/4.4/rhel/7/x86_64/zabbix-release-4.4-1.el7.noarch.rpm
 yum clean all
 yum -y install zabbix-agent
 # Method 2: (Use the zabbix-agent package from another machine to install it directly using rpm)
 rpm -ivh zabbix-agent-4.4.1-1.el7.x86_64.rpm

# Modify zabbix-agent configuration and start the service vim /etc/zabbix/zabbix_agentd.conf
 Server=192.168.244.144
 Server=192.168.244.144 //IP address of the monitoring host Hostname=agent1.zabbix.com //Name of the monitored host to the monitoring host UnsafeUserParameters=1

 systemctl start zabbix-agent
 ss -antp |grep 10050
# Next, we will go to the web side to operate # In order to facilitate service management and easy viewing.
# In the monitoring system, hosts of the same type are often divided into the same host group based on the monitored host roles or other attributes. 

If you wait for a while and there is no red warning in the availability area, it means that the host has been added, but because the template has not been mounted and the monitoring item has not been created, we will try to mount the template and then create the monitoring item.

We install an nginx on the agent side, then go to the zabbix web side to find this template and mount it.

yum -y install nginx
systemctl start nginx 

5. Test monitoring host

Next, we use a browser or elinks to access nginx, generate some data, and then go to zabbix to view the changes

elinks --dump 116.196.83.113

When we customize Key monitoring items in the future, we should first check whether there is any latest data. If no data comes, don't mention the graphic trigger alarm.

At this point, adding local hosts, remote hosts, creating host groups, and mounting templates are complete.

6. Zabbix monitoring items

Monitoring Items

Monitoring items are the basis for obtaining data in Zabbix. Without monitoring items, there is no data - because a host only has monitoring items that define a single indicator or data to be obtained. Monitoring items are suitable for collecting data. Multiple similar monitoring items can be defined as an application set, such as MySQL add, delete, modify, and query, as well as the table reading and writing speed per second can be written as a Mysql application set.

For the example of monitoring items, you need to enter the following necessary information

name

Enter CPU Load as the value, and this value will be displayed as the monitoring item name in the list and elsewhere.

value

Manually enter system.cpu.load as the value. This is a technical name for the monitoring item and is used to identify the type of information to be obtained. This specific value needs to be one of the predefined values ​​of Zabbix Agent.
https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/zabbix_agent # This URL is the predefined value of the zabbix official website.

Information Type

Select Numeric(float) here. This property defines the format of the data. You also need to reduce the number of days of monitoring item history retention to 7 or 14 days. For databases, best practice is to avoid the database retaining too much historical data.
Once we have selected the data type, keep the other options at their default values ​​for now.
1> Disk capacity units are generally B
2> The unit of network card traffic is bps
3> Mysql access volume per second qps, such as MySQL select, insert Mysql serlect per second

Click Add and the new monitoring item will appear in the monitoring item list.

7. View the data

When a monitoring item is defined, you may be curious about what specific value it obtains. Go to the monitoring homepage, click Latest Data, and select the corresponding host to see if the data can be obtained and whether it is the type you want.

chart

After the monitoring item has been running for a while, you can view the visual chart. If you don’t have one, you can create one yourself. The following will introduce it in detail.

8. Common monitoring items

1. Server network interface inbound and outbound traffic and total traffic net.if.in[if,<mode>]
 net.if.out[if,<mode>]
 net.if.total[if,<mode>]

2. The remaining space of the server boot partition vfs.fs.size[fs,<mode>]
 vfs.fs.size[/boot,free]

3. Monitor virtual machine memory vm.memory.size[<mode>]
 vm.memory.size[total
 vm.memory.size[free]
 vm.memory.size[wired]

4. Server service status net.tcp.listen[port]
 net.tcp.port[<ip>,port]
 net.tcp.service[service,<ip>,<port>]
 net.tcp.service.perf[service,<ip>,<port>]

5. Number of server processes proc.num[<name>,<user>,<state>,<cmdine>]
 zabbix_get -s 39.108.140.0 -k proc.num
 121
 zabbix_get -s 39.108.140.0 -k proc.num[,,run]
 3
 zabbix_get -s 39.108.140.0 -k proc.num[,,sleep]
 118

6.Server CPU status (floating point, no unit) 
 system.cpu.intr
 system.cpu.load[<cpu>,<mode>]
 system.cpu.num
 system.cpu.switches
 system.cpu.util[<cpu>,<type>,<mode>]
 zabbix_get -s 39.108.140.0 -k system.cpu.load[all,avg1]
 0.000000
 zabbix_get -s 39.108.140.0 -k system.cpu.load[,avg5]
 0.010000

7. Disk IO status vfs.dev.read[device,<type>,<mode>]
 vfs.dev.write[device,<type>,<mode>]
zabbix_get -s 39.108.140.0 -k vfs.dev.read[/dev/vda1]

8. Monitor file modification vfs.file.chsum[file] # For example, monitor /etc/passwd, /etc/group files to know whether new users are created vfs.file.md5sum[file]
 vfs.file.size[file] # Usually used to monitor logs vfs.fs.size[fs,<mode>]

9.Disk total.

10. Monitor network card traffic

We first create an application set, so that the upload, download, and total traffic of the network card created later will not be very messy, they are all in a Network application set, and can be exported into an XML file and put on other zabbxi hosts for direct use.

What we are doing now is to create monitoring items using the built-in monitoring items installed by zabbix. It is similar to custom keys. We write a monitoring script and then pass parameters. Each key value is equivalent to a monitoring script

Next, we check ---> Host Group to check the latest data. We can see from the figure below that there is data.

Downlink bandwidth and upstream bandwidth.

Download is in, and the downstream bandwidth is what you send out. As a server, the upstream bandwidth must be high. At home, the downstream bandwidth is high. For the server, it needs to receive very few data packets and reply to many data packets. At home, we send out a very small data packet and return the entire web page.

Next, we will create a network card to output traffic, and then make them into an icon to display them graphically.

Next, we will check the latest data in the monitoring. You can develop this habit, because the latest data means that there is no problem with the data flow. If the data has not come and you create a graph, the chart says there is no data, and you think you have to wait for a while, which wastes time and affects efficiency.

As you can see, both monitoring items have data. Next, let's create a graph.

Next, we go to View Monitoring--->Graphs, select the corresponding group, the corresponding host and the created graph

This host can install an nginx, then upload a larger picture to the website root directory, then access it, and then view the network fluctuation graph.

Or we can directly upload a larger rpm or tarball to another host.

11. Monitor CPU

Just like before, create a CPU application set for easy management and summary

Next, we create monitoring items for the application set, cpuintr, cpu interrupt count

Next, we create a CPU load monitoring item every one minute. Through the figure below, we can see that each monitoring item has data coming in. Next, we create a graph

We can see that data can be converted into icons in real time. Next, we will make an aggregated graph.

12. Create aggregate graphics

At this point, our first constructor is completed. The other constructor is the same. I will not write it here, just look at the result diagram.

Creating system-defined monitoring items is similar to the above two. You will get used to it if you practice more. If you are not used to using the officially defined keys, you can write your own scripts to customize the keys according to the company environment. This chapter is over.

Summarize

This is the end of this article about the example code of Zabbix configuration monitoring items and aggregate graphics. For more relevant Zabbix configuration monitoring items and aggregate graphics content, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!