1. configure the discovery rule server side
configuration - automatic discovery
Configuring agent terminal
RPM -Uvh https://repo.zabbix.com/zabbix/4.2/rhel/7/x86_64/zabbix-release-4.2-2.el7 .noarch.rpm
yum the install ZABBIX agent -Y-
## source installation configuration, yum install agent terminal
Vim /etc/zabbix/zabbix_agentd.conf
Serve, # = 192.168.0.13 passive mode to pull data server
ServerActive = 192.168.0.13 # active mode active agent to upload data
configuration to better monitoring - automatic discovery inside to see
here you can see, the device has already been found
3. create action will automatically discover a host of automatic link template
I created three rules must also met in order to trigger actions in the operation
a host IP addresses 192.168.0.10 to 192.168.10.20 must be
type B must be added to the client agent to transfer data
C system.uname I just add this key is to get OS information, which must include in order to trigger a Linux, meaning that this action is in operation only for linux host with the
previous three conditions are met, on the implementation of the following four operations
to send information on the main line to the Admin user ( If you define a good media can send Email), add a host, the host group rules, connection template
content
发现: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}
发现规则:{DISCOVERY.RULE.NAME}
装置IP:{DISCOVERY.DEVICE.IPADDRESS}
装置DNS:{DISCOVERY.DEVICE.DNS}
设备状态:{DISCOVERY.DEVICE.STATUS}
设备正常运行时间:{DISCOVERY.DEVICE.UPTIME}
设备服务名称:{DISCOVERY.SERVICE.NAME}
设备服务端口:{DISCOVERY.SERVICE.PORT}
设备服务状态:{DISCOVERY.SERVICE.STATUS}
设备服务正常运行时间:{DISCOVERY.SERVICE.UPTIME}
4. View
the report - Action Log in to see here is a failure, I did not send Email to define alarm media failure, it does not matter, and on-line, on-line has been successful
here you can see number 16 ip inside the host has been configured