To help you detect and address changing demand for resources, the platform's control features include monitoring alerts with notifications, action plans for automation, and autoscaling.
|Metric||A built-in metric that is provided by a hypervisor or provider (e.g. CPU usage) or a custom metric that the user creates and populates using API calls|
|Alarm||An alarm activates when a metric passes a certain threshold. |
If you imagine a dashboard for your metrics, alarms are like red lights that light up when conditions change, for example, when there is a problem.
See Manage cloud alarms and Infrastructure Alarms
|Alert||An alert enables you to configure notifications or actions from alarms. |
Alerts are like a worker monitoring a group of alarms; when all the lights for the group are lit up, the alert is activated.
Alerts can trigger action plans.
|Action plan||A sequence of actions to perform on entities on the platform, such as VMs or scaling groups. An action plan is run by a trigger.|
|Trigger||A trigger is an alert or a schedule that will run the action plan, for example, during times of increased demand.|
|Scaling group||For horizontal autoscaling, create a scaling group for a VM with rules to define how the platform should scale it out. |
You can then include scaling operations in an action plan.
|Vertical scaling||Vertical scaling means scaling up, adding more resources to an existing VM, for example, boosting your CPU and or RAM capacity.|
|Horizontal scaling||Horizontal scaling means scaling out, deploying more VMs when you need more resources.|
The platform's Alerts feature enables you to track and act upon changes in your cloud environment. To configure Alerts do these steps:
Create alarms for built-in metrics, scaling group metrics, and custom metrics as required
Create alerts to notify users
To create an alert:
Enter the alert details and assign alarms as described below
Name of the alert. The name can contain up to 128 characters
|Description||Describe the alert|
|Muted||Select this checkbox to disable action when the alert is activated|
|List of email addresses to notify when the alert activates. Click Add email to save an address|
Click the + add button to assign alarms to the alert.
You must assign at least one alarm to be able to save the alert. Select an existing alarm, or create a new alarm, and assign it to the alert. Repeat for the required alarms
You can filter the Alarms list by Metric and also if the alarm is Active or not.
Define scaling groups for VMs. The base VM can be deployed or undeployed. See Manage Scaling Groups
To use autoscaling in the same provider, while you are creating the scaling group, select the Create autoscaling action option
After you save the scaling group, select the Metric(s) that will drive the scaling
The platform will automatically create scaling actions that are driven by alarms and alerts on your metrics.
To list the alarms, alerts, and action plans created by the platform, display or edit the scaling group.
If the scaling group is in Maintenance mode, click the pencil edit button
Then go to Autoscaling action and click Show more
You can later display and modify the components of the autoscaling action in the platform. Just go to Virtual datacenters → Alarms, Control → Alerts, and Control → Action plans
The autoscaling actions configure cloudbursting in the same cloud provider as your original VM with metrics. To configure cloud bursting across providers, you can link an autoscaling group in another provider to your original VM metrics.
To trigger scaling on a schedule, skip the alarm and alert steps and create an action plan with actions on the scaling group and one or more schedule triggers. You do not need to create alarms and alerts, but you may like to create them anyway, because they can be very useful to help you control your cloud resources.
The following steps describe how to manually enable autoscaling, so that you can configure cloud bursting across providers.
To manually create autoscaling actions:
Create alarms for built-in metrics, scaling group metrics, or custom metrics. See Custom Metrics Resources. To work with auto-scaling, we recommend that you create alarms for both the high threshold, when you will require more resources, and the low threshold, when these resources can be retired
The name of the action plan
|Description||A description of the action plan|
Action Notes and Parameters table
|Action||Notes and Parameters|
|Decrease CPU||vCPUs. Not supported by hot-reconfigure. Check OS compatibility|
|Set hardware profile||Select from the available hardware profiles|
|Send webhook||See webhook parameters table|
Webhook action attributes table
|Endpoint||Where to submit the request||true|
|HTTP Method||The type of request can be GET, POST, or PUT||false||GET|
|Expected HTTP status code||If this status code is returned, continue running the action plan||false||204 No Content|
|Request headers||Headers such as, secret, authentication, and content-type||false|
|Request content||Request body||false|
When you create actions on VMs also consider the following constraints.
For the API, note that you can request the JSON schema for each action plan entry type from the API.
To run your action plan based on metrics, select an existing alert with these steps:
To run your action plan automatically at selected dates and times, create a schedule trigger with these steps: