Monitoring is a tab where you can monitor the load and performance of an instance using ten metrics.
|1. CPU Utilization|
|2. RAM Utilization|
|3. Network BPS ingress|
|4. Network BPS egress|
|5. Network PPS ingress|
|6. Network PPS egress|
|7. sda/Disk IOPS read|
|8. sda/Disk IOPS write|
|9. sda/Disk BPS read|
|10. sda/Disk BPS write|
To open the tab, select the required instance and click "Monitoring".
Buttons above the graphs control the display of statistics: the left one sets up what period to show, the right one — how often the data will be updated on the screen.
Please note: as a second metric (for example, the number of bits per second), Monitoring displays the average value for one minute. The system collects the volume of traffic/operations for a minute and divides it by 60.
1. CPU Utilization is the load on the machine's CPU, measured as a percentage.
For example, if all cores are 90% loaded, you will see a value of 90%.
CPU Utilization can exceed 100%. This means that the instance used more physical resources than provided for by the tariff at a particular moment. This usually happens during the creation of the instance. This is normal and does not affect payment.
2. RAM Utilization is the amount of RAM that the instance uses to perform tasks.
Measured in percentages, 100% means a full load of RAM.
Inside the system, you can see the RAM Utilization value that is less than in the Monitoring. This is normal: our Monitoring includes cache RAM in the statistics. This is unused RAM that the machine borrows and uses to make applications run smoother and faster. If some application needs more RAM, the system immediately brings it back from the cache.