Abiquo 4.4 enables users to create alarms on metrics across the cloud. In particular, users can select the following objects from the cloud or infrastructure lists in order to create alarms on their metrics:
You can use built-in or custom metrics to create alarms for VMs and scaling groups. For all other entities, you can create alarms on custom metrics.
In Abiquo 4.4, scaling group metrics are now separate from VM metrics. The platform still configures the same metrics used in the base VM for the scaling group, but the platform stores them with the scaling group.
There are two new alarms tabs to replace the VM Alarms tab. Both of these tabs have expanding lists where you can select entities.
Virtual datacenters → Alarms
Infrastructure → Alarms
To create an alarm, select an entity from the list and click + to create an alarm, then complete the dialog.
|Entity type||Select an entity with metrics from the list on the left.|
|Entity name||The name of the entity|
|Entity label||The label of the entity, which for VMs is shown in the list on the left|
|Entity icon||The icon that the platform displays in the UI for VMs and virtual appliances|
Name of the alarm with up to 128 characters. Alarm names must be unique for each metric
|Description||Description of the alarm. Used together with the alarm name and VM name to identify the alarm, for example, when creating an alert|
|Metric||Select one of the metrics available for the VM|
|Metric unit||The unit of the metric. Read only|
|Metric description||The description of the metric. Read only|
|Dimension||When the metric has multiple dimensions, optionally select one or more dimensions. For example, if a VM has multiple hard disks, then the disk read bytes metric may have a dimension for each disk|
Last datapoints in period
The number of datapoints that the platform will evaluate the metric during the elapsed time.
If you request the evaluation of an alarm more frequently than metric data is collected by the platform or sent by the provider, then the alarm will not activate.
We recommend that you create alarms with longer evaluation periods, for example, an average of 10 points over the last hour, so the transmission and collection intervals will not affect the activation of the alarm.
Statistic that the platform will use for evaluating the alarm, which can be: average, maximum, minimum, sum, count, dev
Operator that the platform will use for evaluation of the alarm, for example, greater than. Values can be: notequal, greaterthan, greaterthanorequalto, lessthan, lessthanorequalto, trendup, trenddown
Value that the platform will evaluate the alarm against, if appropriate