Purpose:
Reports the resource allocation problems such as approaching or exceeding certain limits.
Event specification:
Name |
Min/Max |
Type |
|
|
Subscription name:
alerts_subscription
See subscribe
for more information about subscriptions.
Description:
This event triggers when an alert is raised on a server. The event reports alerts for every server that the Agent is aware of. If you subscribe to the event on the Master Node in a Virtuozzo group, you will receive the alert notifications about every server in the entire group.
The resource_alert
element substitutes the event_data
element in the eventType
structure.
Some of the alerts deal with the resource allocations. Resource alert is a notification about some parameter of the system, getting over some barrier, or coming close to some limit. Usually they are used for monitoring of the environment health, predicting its performance, or collecting information about the settings in need of tuning.
There are four possible alert levels:
Alert level |
ID |
Description |
Green |
0 |
Everything is fine. This alert is raised when one of the higher-level alerts is canceled. |
Yellow |
1 |
Moderately dangerous situation. The specified parameter is coming close (within 10%) to its soft limit barrier. |
Red |
2 |
Critical situation. The parameter exceeded its soft limit or came very close to the hard limit. Depending on the parameter type, either some process can be killed at any time now, or the next resource allocation request can be refused. |
Black |
3 |
The hard limit was reached and the resource allocation was refused, or some process overusing the resource was killed. Once raised, a black alert remains in effect for 5 minutes. |
It is always a good idea to check and adjust the QoS configuration parameters upon receiving an alert.
Example:
Input
<packet version="4.0.0" id="2">
<data>
<system>
<subscribe>
<name>alerts_subscription</name>
</subscribe>
</system>
</data>
</packet>
Output:
<packet version="4.0.0" time="2006-08-18T10:47:43+0000">
<target>events_subscription</target>
<target>alerts_subscription</target>
<src>
<director>gend</director>
</src>
<data>
<event>
<eid>ccc794ad-cc5d-49f2-8d84-6631263c81be</eid>
<time>2006-08-18T10:47:43+0000</time>
<source>resource_alert_monitor</source>
<category>resource_alert</category>
<sid>XXX</sid>
<data>
<resource_alert>
<eid>13a10bc2-3ace-4bf9-ac0f-e33d98b1766d</eid>
<type>1</type>
<class>counters_vz_ubc</class>
<counter>numproc</counter>
<cur>8</cur>
<hard>10</hard>
</resource_alert>
</data>
<info>
<message>
UmVzb3VyY2UgJXR5cGUlICVpZCUgYWxlcnQgb24gZW52aXJvbm1lbnQgJWVpZCUgY3VycmVudCB2YWx1ZTogJWN1ciUgc29mdCBsaW1pdDogJXNvZnQlIGhhcmQgbGltaXQ6ICVoYXJkJQ==
</message>
<name></name>
<translate/>
<parameter>
<message>OA==</message>
<name>cur</name>
</parameter>
<parameter>
<message>MTNhMTBiYzItM2FjZS00YmY5LWFjMGYtZTMzZDk4YjE3NjZk</message>
<name>eid</name>
</parameter>
<parameter>
<message>MTA=</message>
<name>hard</name>
</parameter>
<parameter>
<message>bnVtcHJvYw==</message>
<name>id</name>
</parameter>
<parameter>
<message></message>
<name>soft</name>
</parameter>
<parameter>
<message>eWVsbG93</message>
<name>type</name>
<translate/>
</parameter>
</info>
</event>
</data>
</packet>