• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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