5.5. Viewing Infrastructure Logs¶
This section provides information on the Infrastructure level logs.
5.5.1. Viewing Infrastructure Task Logs¶
You may turn to the Tasks subtab to check the status of any Virtuozzo Automator operation recently performed.
The tasks list is presented as the following table:
Column |
Description |
---|---|
Time |
The date and time when the execution of the task was started. |
Hardware Node |
The physical server or the Master Server where the task is performed. This option is available only at the Infrastructure level. |
Object |
The name of the virtual environment or other object that is performing the task. |
Task |
The kind of the task. |
User |
The user who initiated the process. |
Status |
Indicates whether the task was successful or failed. |
Details |
The detailed information on a particular task. Click the Details link opposite the needed task to view the details. |
To show or hide columns, click Select Columns and set or clear the respective checkboxes.
By default, 20 records are displayed on a page. To change the number of records shown per page, click the appropriate link below the table. You can also filter the log records shown in the Tasks table. To do that, click Show Search, enter search patterns in the search fields, and click Search. To change what search fields are displayed, click Customize. Click Reset Results to view all log records.
5.5.2. Viewing Infrastructure Alert Logs¶
The Alerts subtab enables you to view the physical and virtual environment resource consumption.
Every time a physical server or any of its virtual environments 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. You shall pay attention to the problem resource and correct the situation.
The Alerts table provides you with the following data:
Column |
Description |
---|---|
Time |
The date and time when the alert was generated. |
Object |
The physical server the alert was logged for. |
Category |
One of the two alert categories: Resource (alert on a single virtual environment’s resource consumption) or Group (alert on the whole Group’s resource consumption). |
Details |
The problem description. |
Type |
The alert sign displays the type of alert for the given virtual or physical server. See the detailed description below. |
Parameter |
The type of the resource that required the consumption value alert due to its overusage. |
To show or hide columns, click Select Columns and set or clear the respective checkboxes.
You can filter the alerts shown in the Alerts table. To do that, click Show Search, enter search patterns in the search fields, and click Search. To change what search fields are displayed, click Customize. Click Reset Results to view all alerts.
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 differs slightly depending on the parameter under alert.
For CPU-related parameters the meaning of the three zones is the following:
Zone |
Description |
---|---|
Green |
The physical server (or virtual environment) consumes less than 85% of the CPU time allowed to it. This means that you can run more applications inside the physical server (or virtual environment) without violating the performance of the current ones. If the physical server consumes more than 85% of the allowed CPU time, but for an insignificant time, the color remains green as this situation is not dangerous. |
Yellow |
The physical server (or virtual environment) consumes between 85% and 95% 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 physical server might experience shortage of available CPU power. You may need to consider the possibility of cutting down the number of processes. |
Red |
The physical server (or virtual environment) consumes more than 95% 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 physical server caused by a temporary task. For example, this may happen if you are compiling a package in the physical server (or virtual environment) 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 VA System processes page to determine which processes 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 physical server (or virtual environment) consumes less than 85% of disk resources allowed to it. This means that the physical server has currently no problem with disk resources. |
Yellow |
The physical server (or virtual environment) is using between 85% and 95% of the disk resources available to it on the
physical server. The situation is rather dangerous since the next disk resource allocation request can be refused by
the physical server (or virtual environment). Therefore, you should erase unnecessary data from the physical server
immediately. A physical server (or virtual environment) is allowed to consume more than 95% of its disk quota only
during the grace period (see the |
Red |
The physical server (or virtual environment) has exceeded the soft limit and a disk resource allocation has been refused by it. This might have resulted in a loss of some valuable data or other problems inside the physical server. To discontinue this very serious situation, you should erase unnecessary data from the physical server immediately. |
For memory-related parameters the meaning of the three zones is the following:
Zone |
Description |
---|---|
Green |
The physical server (or virtual environment) consumes less than 85% of the memory-related resource allowed to it. |
Yellow |
The physical server (or virtual environment) consumes between 85% and 95% 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 physical server 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 physical server (or virtual environment) has been denied this memory-related resource due to its overusage. This might have resulted in application crashes or other problems inside the physical server (or virtual environment). |
By default, the zone threshold values (the soft and hard limits) are 85% and 95% of the resource. It is possible to customize these values for a single node or for all nodes registered in Virtuozzo Automator.
You can change zone threshold values for a single node as follows:
On a slave node, change the
yellow_alerts_threshold
andred_alerts_threshold
values in the/var/opt/pva/agent/etc/vzagent.conf
file as required.Restart VA Agent:
on a Virtuozzo 6 node
# service pvaagentd restart
on Virtuozzo Hybrid Server 7 node
# systemctl restart va-agent
If you want to change zone threshold values for all nodes in the infrustructure, for example, to 80% for the soft limit and to 90% for the hard limit, run the following commands in the VA Management Node console:
# vzagroup reconfigure /data/resource_alert_monitor/configuration/yellow_alerts_threshold 80
# vzagroup reconfigure /data/resource_alert_monitor/configuration/red_alerts_threshold 90
5.5.3. Viewing Infrastructure Event Logs¶
The Events subtab keeps track of all the changes in the statuses of all the virtual environments registered on Virtuozzo Automator physical servers. These changes may happen due to the virtual environment routine management via Virtuozzo Automator, command line operations, or due to the operation of some programs.
The Status Changes table on the Events subtab displays the information on the physical server and virtual environment changes as follows:
Column |
Description |
---|---|
Time |
The time when the status of a physical server or virtual environment was changed. |
Object |
The name of a physical server or virtual environment whose status was changed. |
Old Status |
The previous status of a physical server or virtual environment. |
Status Obtained |
The current status of a physical server or virtual environment. |
To show or hide columns, click Select Columns and set or clear the respective checkboxes.
By default, 20 records are displayed on a page. To change the number of records shown per page, click the appropriate link below the table. You can also filter the log records shown in the Events table. To do that, click Show Search, enter search patterns in the search fields, and click Search. To change what search fields are displayed, click Customize. Click Reset Results to view all records.