System: CentOS7
Software: VMware workstation
Network connections: bridge mode
Deployment: server-side and end agent deployed on the same virtual machine
Agent modes: passive mode
Added: Process passive mode
A, zabbix installation and set up early
Installation Reference document: https: //www.cnblogs.com/Sungeek/p/9069999.html
Two, agent configuration
The content of /etc/zabbix/zabbix_agentd.conf emptied into the following restart zabbix_agent: server side i.e. localhost (127.0.0.1)
PidFile=/var/run/zabbix/zabbix_agentd.pid LogFile=/var/log/zabbix/zabbix_agentd.log LogFileSize=0 ListenPort=10050 ListenIP=0.0.0.0 Server=127.0.0.1 #ServerActive=10.27.146.250 Hostname=Zabbix server Include=/etc/zabbix/zabbix_agentd.d/
systemctl restart zabbix-agent.service
Third, the interface configuration
1. Function Point: interface => host => Create the host
2. The host name and port agent with zabbix_agentd.conf files Server Hostname and consistent, the default port 10050
3. Add the template Template OS Linux
4. Go back to the host page where you can see the availability of the green
5. each monitored item to view graphic
Functions: Monitoring => Graphics
Supplement 1: Basic Troubleshooting
1. After configuring zabbix can detect whether the configuration by zabbix_get
2. Check the agent and server-side log for error
tail -100f /var/log/zabbix/zabbix_server.log
tail -100f /var/log/zabbix/zabbix_agentd.log
3. Check whether the latest data table (the timestamp of the second column into Beijing, link: https: //tool.lu/timestamp/)
MariaDB [zabbix]> use zabbix;
MariaDB [zabbix]> select * from history;
Distinguish between active and passive mode agent mode: Supplement 2
1. Passive mode: Server waiting for collection each time you connect Agent
work process:
2. Active Mode: Agent will send the collected data to the active server
work process:
So the use of the active mode will have better performance zabbix_server