• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Meaning of different units in health monitor

Bitpalast

Plesk addicted!
Plesk Guru
In the Health Monitor extension detail charts we are seeing different units on the ordinate for Apache load, Nginx load, mail load, MySQL load and Plesk load. The units (symbols) are:

k
m
no symbol [none]

Should not k be x1000 and m x1000000? However, we we doubt that the system has measured a 5000.0 index on CPU load when it displays "5.0 k", or 200 million load index on mail load when the chart displays "200 m", 2 million load index on Plesk load for "2.0 m" and so on ... All of our hosts have a low load only, so why are the charts showing such high numbers?

What is the true meaning of these ordinate abbreviations?
 
*lightbulb* The "m" is not "Mega", but "milli", so 500 m = 0.5, 450 m = 0.45 and so on.

k still pending. Indeed it looks as this means "kilo" as expected. But than the question is why for rare and short moments the load is measured excessively and unrealistically high while the server is operating trouble-free?
 
Back
Top