|
|
|
|
Every time a Container consumes more of a resource than is specified by the limit on that resource, or is coming close to that limit, an alert is generated and logged. Turn to the Managing and Monitoring Container Resources section to know more about the limits for the corresponding resources. You shall pay attention to the problem resource and correct the situation.
Note: The same information for a single Container is also accessible if you follow the Resource Alerts link on the Logs tab of the corresponding Container dashboard.
You may have the Alerts table display only those alerts that have a particular date, relate to a particular category or parameter, are logged for the Container with a particular ID or hostname, or for a particular Hardware Node. Over the table, click the Show Search link to display the fields where you can specify the parameters that the log should meet; then click the Search link.
The Alerts table provides you with the following data:
Time |
The date and time when the alert was generated. |
Category |
One of the two alert categories: Resource (alert on a single Container's resource consumption) or Group (alert on the whole Virtuozzo Group's resource consumption). |
Details |
Detailed information on the alert. |
Hardware Node |
The Node hosting the Container that has generated the alert. |
Container |
The name or ID of the Container that has generated the alert. |
Type |
The alert sign displays the type of alert for the given Container. See the detailed description below. |
Parameter |
The type of the Container resource that required the consumption value alert due to its overusage. |
|---|
There are three alert types in total that have a visual representation in the Type column and correspond to the three resource consumption zones. A green circle with a white tick means the green zone, an orange circle with a white exclamation mark points to the yellow zone, and a red circle with a white exclamation mark refers to the red zone.
The meaning of these zones differ slightly depending on the parameter under alert.
For CPU-related parameters the meaning of the three zones is the following:
Zone |
Description |
Green |
The Container consumes less than 90% of the CPU time allowed to it. This means that you can run more applications inside the Container without violating the performance of the current ones. If the Container consumes more than 90% of the allowed CPU time, but for an insignificant time, the color remains green as this situation is not perilous. |
Yellow |
The Container consumes between 90% and 100% of the CPU power allowed to it for a relatively long while. Usually this means that the running processes consume too much CPU power. It is up to you to decide whether this situation suits you, but you should bear in mind that additional applications launched inside the Container might experience shortage of available CPU power. You may need to consider the possibility of cutting down the number of processes. |
Red |
The Container consumes 100% of the CPU power allowed to it, i.e. all the available CPU power, for a long time. Usually this means that currently there is some CPU-intensive process inside the Container caused by a temporary task. For example, this may happen if you are compiling a package in the Container or in similar cases. In this case you should simply wait for this task to complete. However, if you do not know the reason for the CPU overconsumption, turn to the Parallels Infrastructure Manager System processes page to determine which process(es) are causing the problem and take the corresponding measures. For example, you might want to terminate or kill the offending process. Otherwise, the system performance may continue low for a long while. |
For disk-related parameters the meaning of the three zones is the following:
Zone |
Description |
Green |
The Container consumes less than 90% of disk resources allowed to it. This means that the Container has currently no problem with disk resources. |
Yellow |
The Container is using between 90% and 100% of the disk resources available to it on the Hardware Node. The situation is rather dangerous since the next disk resource allocation request might be refused to the Container. Therefore, you should erase unnecessary data from the Container immediately. On a Linux Node, a Container is allowed to consume more than 100% of its disk quota only during the grace period (see the |
Red |
The Container has exceeded the soft limit and a disk resource allocation has been refused to it. This might have resulted in a loss of some valuable data or other problems inside the Container. To discontinue this very serious situation, you should erase unnecessary data from the Container immediately. |
For memory-related parameters the meaning of the three zones is the following:
Zone |
Description |
Green |
The Container consumes less than 90% of the memory-related resource allowed to it. |
Yellow |
The Container consumes between 90% and 100% of the memory-related resource allowed to it. It is up to you to decide whether this situation suits you, but you should bear in mind that additional applications launched inside the Container might experience shortage of the corresponding resource. Judging by the offending resource, you might determine the reason for its shortage and take the corresponding measures. |
Red |
The Container has been denied this memory-related resource due to its overusage. This might have resulted in application crashes or other problems inside the Container. |
