Entry to monitoring-Linux average load (load average)

Monitoring entry-Linux average load (load average) has recently been harassed by average server load alarms, but cannot be found when you log on to the server. therefore, it is suspected that the threshold value of the load is set improperly. how many settings are reasonable? Let's take a look at the basic knowledge. the average load of www.2cto.com refers to the average utilization rate of the system's running queues. It can also be considered as the average rate of processes that can run. generally, a process consumes resources such as CPU, memory, disk I/O, and network I/O. In this case, the average load is not an independent CPU usage. memory, disk, network, and other factors can also affect the average load of the system. in a single-core processor, when the average load is 1 or less than 1, the system processing process is very easy, that is, the load is very low. when it reaches 3, it will appear very busy. when the number reaches 5 or 8, the process cannot be well processed. (5, 8 is still a controversial threshold. To keep it conservative, choose a low one .) for example, my server has two CPUs. each six cores is equivalent to a 12-core processor. if the load is less than 12, the server utilization is low. if the load is greater than 12 and less than 36, the server utilization rate is relatively high. In this case, you should consider optimizing the service or replacing the faster CPU. if the server load is greater than 36, less than 60, or even greater than 60, the server is very dangerous and may cause problems at any time. after the above analysis To obtain the average load of the system. average load value of topuptimew, for example, load average: 0.08, 0.03, 0. 00. these values indicate the average load of the system in the last 1/5/15 minutes. so which value should we take for determining if the load is too high? Based on experience: we should focus on the average load of 5/15 minutes, because the average load of 1 minute is too frequent, and the high concurrency at an instant will lead to a significant change in this value. combined with the nagios alarm, the 12-core server plans to make the following alarm settings: check_load-w, 12-c 60, 48, 36