11.1.3.1. Creating Monitoring Alarm¶
At the Create Alarm screen of Monitoring, the following 4 items are required to be defined:
Basic Information of your alarm |
Enter your alarm name (Alarm Name), and its details (Description and Severity). |
Conditions of your alarm (Threshold) |
Define the relevant thresholds for each resource and meter. |
Action for the alarm occurrence |
Define conditions for of the action (exceeding or falling below the relevant threshold),
the type of action (Email notification or API posting), and
details of the action (Email address receiving the notification or API request sentences).
|
Advanced settings |
Define necessary rules for making statistics on the alarm.
At the Advanced Settings, the following 5 items are available to be defined:
*Period ・・・ specify the scope of statistic information to be generated by seconds.
*Statistics ・・・ Select a statistics type adapted (count/sum/avg/min/max).
*Evaluation Periods ・・・ Specify the number of evaluations made on the acquired statistics data.
*Evaluation Type ・・・ Specify the action execution conditions. (Select "and" for executing the specified action when all of each evaluation meets conditions. Select "or" for executing the specified action when more than two evaluations meets conditions.)
*Repeat Actions ・・・ Choose either on or off for making the alert repeatedly. (If set to Repeat Notification, alarm action is executed every 5 minutes while ALARM status is ongoing.)
If you want to execute the alert when a sample value exceeds or falls smaller than the relevant threshold more than once, this Advance Settings is not required.
|
Note
Keep-alive monitoring shows 0 for normal or 1 for outage.
Note
The number of actions taken for alarming is 5 at maximum.
[Examples] Creating Alarms for High CPU Usage¶
Note
In the example above, if you want to receive the notification email when the alarming status turns from ALARM to OK (when the CPU usage becomes lower than 80%) as well, add an action taken for the status becomes OK at the section "3. Define Your Alarm Actions".
Note
At the section "3. Define Your Alarm Actions", please make sure to click [ +Add ] after inputting all necessary information so that the action made is added to the Added Actions list.
Note
[ Examples ] Creating Alarms for Instance Shutoff¶
Note
In the virtual server alive monitoring (VirtualMachineStatus) meter, the value indicating the instance stop status is 1.
Note
In the example above, if you want to receive the notification email when the alarming status turns from ALARM to OK (when the instance is back to booting status) as well, add an action taken for the status becomes OK at the section "3. Define Your Alarm Actions".
Note
At the section "3. Define Your Alarm Actions", please make sure to click [ +Add ] after inputting all necessary information so that the action made is added to the Added Actions list.
Note