Preface

In the previous article (Deployment Guide), we successfully deployed the server and agent of wgcloud (see article:Home Data Center Series: Deploying Your Own O&M Monitoring System via wgcloud (Part 1): Deployment Guide) After a period of actual operation, we can finally summarize the functions and basic configuration of wgcloud. After all, O&M still needs to look at the actual effects, and I also adhere to the principle that practice is the sole criterion for testing truth.

Introduction to Monitoring Functions

Monitoring Summary

Here you can see a summary of all monitoring items in wgcloud as well as overall statistics of the resources used:

Resource Management

Resource management is the most important part, and the monitoring targets we usually focus on are all under this item:

Host Management

Here you can see the detailed system information of all hosts where the agent is deployed, including CPU, memory, upload/download rates, number of connections, number of processes, etc., as shown in the figure below:

The host in the red box is my Tencent Cloud Lightweight Cloud Host, which was added via the Tailscale address. The system and charts in the red box on the right show the detailed information of the monitored host in great detail. Below are parts of the system and charts.
System:

Charts:

If the monitored host is a Linux device, you can also directly perform Web SSH under "More" on the right, which is very thoughtful, as shown in the figure below:

Note: Hosts in Host Management cannot be added manually; they are all automatically registered and added by the agent side, so communication between the agent and the server side must be ensured.

Host Abnormal Processes

Here you can see some processes on each host that consume a lot of memory or CPU resources. For example, on my Tencent Cloud Lightweight Server, the Java process occupied 56.16% of CPU resources, so it was judged as an abnormal process:

However, this may be related to the judgment method, and it is not necessarily accurate. It still needs to be viewed in combination with the actual situation on the target host.

Process Monitoring

Here you can add key processes of interest on existing hosts in Host Management by yourself. Just click "Add" in the red box above, as shown in the figure below:

Enter the add interface and add the process as shown in the figure below:

For example, I added monitoring for two key processes, authserver and worldserver, on the World of Warcraft server:

Port Monitoring

Here you can add monitoring for specific ports on existing hosts in Host Management. In fact, if it is just monitoring some externally open ports, solutions like uptime-kuma can also do it. However, the most important role of port monitoring on wgcloud is to monitor ports on the localhost address of the host, which cannot be achieved through external monitoring.
Click "Add" in the red box above:

Add it according to the port information on the host where the port you need to monitor is located. For example, I will use the warp proxy port on my Tencent Cloud Lightweight Server as an example:

After successful addition, you can see the port status:

Log Monitoring

Here you can specify to view logs on a certain host and specify its alarm keywords. This requires some understanding of the log file location and log content of the application on the host. I won't demonstrate it here as I don't have this need for now. You can just take a look at the monitoring settings interface:

File Tamper Prevention

I won't introduce this feature with Chinese characteristics too much. It is similar to the settings of log monitoring. You will understand it by looking at the interface:

Docker Monitoring

Here you can monitor Docker deployed on each host. Again, click the "Add" button in the red box above:

Then fill in the information of the Docker that needs to be monitored as shown in the figure below:

The Docker I actually monitor:

Data Monitoring

The data monitoring part is for databases, where data source management is for specific "databases", and data table monitoring is for a specific "table" in a specific "database":

Data Source Management

The configuration is very simple, just follow the image tutorial below:

Actual effect display:

Data Table Management

This part is mainly to monitor the changes of a certain value in a certain table in a certain database. I have no such need, so I didn't set it. You can configure it according to your own needs. The interface is as follows:

Service Interface Monitoring

This part can use the specified method to access the URL corresponding to the service, and judge its health status according to the returned status code:

Display Dashboard

Network Communication Monitoring

This part of the function is relatively simple, which is to monitor devices through 2 methods: ping and SNMP:

PING Monitoring

Monitoring in this way requires the monitored host to be able to respond to ICMP queries, and may require opening the firewall on the corresponding device. This method can only monitor whether the target is online. The adding method is similar to the previous one, so I won't repeat it, just show the effect:

SNMP Monitoring

This method monitors the target through the SNMP protocol. In addition to whether the host is online, the monitored content can also monitor the traffic, rate, CPU, memory, temperature, voltage, etc. of the incoming and outgoing devices. However, the monitored target needs to support the SNMP protocol, and different functions may need to support different SNMP versions (for example, if verification function is needed, SNMP v3 is required).
The interface for adding monitoring targets is as follows:

The monitoring effect is as follows:

FTP/SFTP Monitoring

This part of the function is very simple, which is to monitor FTP and SFTP servers. Like before, you need to manually add the FTP/SFTP servers to be monitored. The final effect is as follows:

Middleware Monitoring

This part can monitor the following types of content, but it requires a host that can access both the wgcloud server side and the monitored content, and install a component named "server-backup" similar to an agent as an auxiliary tool. I didn't bother with it, those interested can research it themselves.

Introduction to O&M Functions

Inspection Report

wgcloud will generate daily, weekly and monthly inspection reports by default:

The content is relatively simple, the following is part of the daily report content:

System Management

This part has 2 contents, system logs and command delivery, as shown in the figure below:

System logs will display some alarms on each monitored host:

Command delivery can allow the selected monitored host to run commands through the agent, such as database backup. Commands can be run immediately or executed regularly (multiple times):

Alarm Settings

This part of the content is very simple, divided into 3 parts, you will understand by looking at the configuration pages of these 3 parts.

Email alarm, set the mailbox information to receive alarms:

Script alarm:

Custom alarm, customize the alarm items and thresholds of the monitored host:

Asset Management

Provide simple asset management functions:

Device Account Management

Provide simple device account management functions:

Summary

Generally speaking, wgcloud is very in line with the usage habits of Chinese people, and the functions provided by the personal free version are enough for ordinary people to use. The only regret is that the limit of 10 monitored targets is slightly small.

Note: 10 is the limit for each function item: such as 10 monitored hosts, 10 monitored processes, 10 monitored Dockers... If you only consider key monitored targets and plan it, it is still enough for ordinary people.