11.1.3.1. Creating Monitoring Alarm¶

This section describes how to create Monitoring Alarms.

To create a new Monitoring Alarm, select [ Alarm ] from Monitoring Control Panel and Click [ Create ] or [ Bulk Create ] on the Alarms section screen.

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.

The following sections show examples of settings for creating alert to notify Virtual server instance (CentOS_Tutorial)'s CPU exceeds the threshold or to notify its instance is stopped.

[Examples] Creating Alarms for High CPU Usage¶

The following shows an example of alarm settings which “send an email notification when the CPU usage excesses the threshold defined at 80%.”

Define a condition that "an alert will be made when the CPU usage becomes larger than 80%" and an action that "to send email notification when the alert is on" which will be taken in case the defined condition is met.

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.

In addition, we will explain an example of alarm setting for advanced settings, “E-mail notification when the CPU usage rate every 5 minutes exceeds 80% for two consecutive times”.

Set “Alarm status is judged when the minimum value (min) of CPU usage for the past 450 seconds exceeds 80% of the threshold”.

Note

In this setting example, the current sample time and two sample values before 300 seconds are used as alarm judgment targets. The CPU usage meter monitors every 300 seconds, but the monitoring interval of monitoring has an error of a few seconds. Set the monitoring interval to 1/2) = 450 seconds.

In addition, it takes at least 10 minutes for the alarm to transition to the ALARM state after the CPU utilization exceeds 80%.

[ Examples ] Creating Alarms for Instance Shutoff¶

The following shows an example of alarm settings which “send an email notification when the target virtual server instance is shutoff.”

Set "Determine ALARM status when virtual server alive monitoring meter is 1 (stopped)" as a condition, and set "Notify by email when transitioning to ALARM status" as an action when the condition is met To do.

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.

In addition, we will explain an example of an alarm setting for advanced settings: “Email notification when the status of a virtual server instance collected every minute is stopped three times in a row”.

Set "Alarm status is judged when the minimum value (min) of virtual server alive monitoring meter for the past 150 seconds is 1 (stopped)"

Note

In this setting example, three sample values from the current time, 60 seconds before, and 120 seconds before are subject to alarm judgment. The virtual server alive monitoring meter monitors at 60-second intervals, but because the monitoring monitoring interval has an error of several seconds, the generation range is to include the sample value before 120 seconds as the alarm judgment target. Set 120+30 (1/2 of the monitoring interval) = 150 seconds.

In addition, it takes at least 3 minutes for the alarm to transition to the ALARM state after the virtual server instance is stopped.

[ Example ] Bulk Creating Alarms for High CPU Usage and Instance Shutoff¶

With the Bulk Creating Alarms function, you can create multiple alarms to a single resource and/or a single alarm to multiple resources.

For the example here, create the alarms to multiple virtual server instance (Ubuntu_Tutorial and RHEL_Tutorial) that “send an email notification when the CPU usage becomes larger than 80%” and “send an email notification when the target virtual server instance is shutoff” together.

11.1.3. Using Monitoring Alarms

11.1.3.2. Managing Monitoring Alarms (Editing and Deleting)