Installation package decompression and directory structure description
The Linux decompression command is as follows. Windows can open the compressed package with the decompression software
tar -xvf wgcloud-v3.4.2-en.tar.gz
2、Description of installation package directory structure
(1) server/ is the server (or master control), which processes the host indicator data reported by the agent, and displays it after comprehensive processing. The API, data monitoring and data communication monitoring (PING and SNMP) are independently monitored by the server and do not rely on agents
What if the server cannot access the monitored data source, service interface, data communication PING and SNMP devices
(2) agent/ is the client (or probe end, controlled end), responsible for collecting various indicators (cpu, memory, disk, process, hardware information, process, port, docker, file security, log file, etc.) of the host, and reporting them to the server regularly (2 minutes by default)
(3) wgcloud-MySQL.sqlInitialize the MySQL database file, wgcloud-PostgreSQL.sql Initialize the file for the PostgreSQL database,wgcloud-Oracle.sql Initialize files for oracle
(4) server/config/application.yml is the server configuration file, server/config/ is the configuration file of the daemon (wgcloud daemon release), agent/config/ is an agent configuration file (all agent configuration files of the same version are consistent)
(5) server/log Is the directory where the server running logs are located, agent/log is the directory where the agent running logs are located. The server and agent logs are reserved for the last 30 days by default
(6) server/logo is used for storing logo images, server/template is a directory with no practical significance, so don't pay attention to it
(7) Finally, after the server and agent deployment are decompressed, the configuration file can be modified slightly to start running without compiling
3、Other instructions
(1) Only one server can be deployed. All agents report the indicator data to this server in a one-way manner
(2) Deploy as many agents as there are hosts to monitor (Start the agent even if the server host needs monitoring), How to deploy agent separately on monitoring host
(3) Server and agent need to keep the same version
(4) Monitoring host information is automatically collected and reported by agent , Therefore, hosts cannot be added to the server host list page . After the agent is deployed and started, you can see the monitoring host on the [Host] page
(5) wgcloud-daemon-release is a daemon. Executing server/ will start wgcloud-server-release.jar and wgcloud-daemon-release at the same time. The daemon should not be closed, and the server should communicate with the daemon
(6) The time of the host system where the server and agent are located should be consistent, Even if there are differences, the time difference shall not exceed 15 hours (In this time difference, the agent prints the tamper proof check failure information, please ignore it, which will not affect the monitoring and collection)
(7) Please be careful not to edit/modify server/wgcloud-server-release.jarOtherwise, the agent log will show tamper proof verification failure information, and the data will not be reported after reaching a certain period
(8) If the agent cannot directly access the server, it can transfer and report the data to the server through the proxy wgcloud proxy, View Description
(9) If the server is deployed and running on Windows, try not to have a space in the directory path where the server is located(Such as C:\Program Files (x86)\wgcloud)Sometimes, low version windows cannot be started because there are spaces in the path
(10) Tips: server and agent can be mixed, as long as the same version is maintained . That is, the server runs on Linux, the agent can run on Linux and Windows, and vice versa
Previous step    Next step