Installation package decompression and directory structure overview
1、 Relieve stress
The Linux decompression command is as follows. Windows can use decompression software to open the compressed file wgcloud-v3.5.2.zip
tar -xvf wgcloud-v3.5.2.tar.gz
2、 Installation package directory structure description
wgcloud-v3.5.2
	│  
	│─sql SQL file for creating initialization tables in the database
	│  │  wgcloud-MySQL.sql MySQL database initialization file
	│  │  wgcloud-Oracle.sql oracle database initialization file
	│  │  wgcloud-PostgreSQL.sql PostgreSQL database initialization file
	│  └─ wgcloud-SQLServer.sql Microsoft SQL Server database initialization file
	│
	├─agent The client (or probe end, controlled end) is responsible for collecting various indicators of the host (CPU, memory, disk, process, hardware information, process, port, Docker, file tamper proof, log files, etc.) data, and reporting them to the server at regular intervals (default 2 minutes)
	│  │  start.sh Start/restart command
	│  │  stop.sh Stop command
	│  │  wgcloud-agent-release Agent program
	│  │
	│  ├─config
	│  │      application.properties Agent configuration file (all agent configuration files of the same version are consistent)
	│  │
	│  └─log The directory where the agent's running logs are located is reserved by default for the last 30 days
	└─server The server (or main control end) processes the host indicator data reported by the agent, and presents it after comprehensive processing. The service interface, middleware, data monitoring, data communication monitoring (PING and SNMP), FTP/SFTP are autonomously monitored by the server without relying on agentsstart.sh Start/restart commandstop.sh Stop commandwgcloud-daemon-release  Daemon processwgcloud-server-release.jar Server process
		│
		├─configapplication.yml Server configuration filedaemon.properties Daemon process port configuration file
		│
		├─log The directory where the server running logs are located is reserved by default for the last 30 days
		└─logo Used for storing logo images
					
(1) What if the server cannot access the monitored data source, service interface, data communication PING and SNMP devices, FTP/SFTP
(2) Both server and agent deployment can be started and run without compiling, after decompression and making necessary modifications to the configuration files
(3) Suggest deploying the agent to the same directory on all controlled hosts for easier management and upgrades in the future
3、 Other instructions
(1) Deploy only one server, and all agents report metric data unidirectionally to this server
(2) Deploy the agent on the host that requires monitoring Even if the server host needs to be monitored, the agent must be started, How to deploy agents separately on the monitoring hostIf you don't want to install an agent on the controlled host, you can also use SNMP monitoring
(3) The server and agent need to maintain the same version
(4) The monitoring host information is automatically collected and reported by the agent, Therefore, the server-side host list page cannot add hosts. After the agent is deployed and started, you can see the monitoring host on the [Host Management] page
(5) wgcloud-daemon-release is the daemon process. Executing server/start.sh will simultaneously start wgcloud-server-release.jar and wgcloud-daemon-release. The daemon process should not be shut down, and the server should communicate with the daemon process
(6) The time of the host system where the server and agent are located needs to be consistent, Even if there are differences, the time difference should not exceed 15 hours (Within this time difference, the agent will print a message stating that the anti tampering verification has failed. Please ignore it as it does not affect monitoring and collection.)
(7) Please be careful not to edit/modify server/wgcloud-server-release.jarOtherwise, the agent log will show a message of tamper proof verification failure, and data will no longer be reported after a certain period of time
(8) If the agent cannot directly access the server, it can use the wgcloud proxy agent to transfer and report data to the server, View
(9) If deploying and running the server on Windows, try not to have spaces in the directory path where the server is located(as C:\Program Files (x86)\wgcloud), Sometimes, lower versions of Windows may encounter issues with startup due to spaces in the path
(10) Tips: Server and agent can be mixed as long as they maintain the same version. The server runs on Linux, the agent can run on Linux or Windows, and vice versa
 
Previous Step    Next Step