- JSON representation
- AutoscalingPolicy
- ScaleInControl
- CpuUtilization
- PredictiveMethod
- CustomMetricUtilization
- UtilizationTargetType
- LoadBalancingUtilization
- Mode
- ScalingSchedule
- Status
- StatusDetails
- ErrorType
- ScalingScheduleStatus
- State
Represents an Autoscaler resource.
Trusted Cloud Compute Engine has two Autoscaler resources:
Use autoscalers to automatically add or delete instances from a managed instance group according to your defined autoscaling policy. For more information, read Autoscaling Groups of Instances.
For zonal managed instance groups resource, use the
autoscaler
resource.
For regional managed instance groups, use the
regionAutoscalers
resource.
JSON representation |
---|
{ "kind": string, "id": string, "creationTimestamp": string, "name": string, "description": string, "target": string, "autoscalingPolicy": { object ( |
Fields | |
---|---|
kind |
[Output Only] Type of the resource. Always
for autoscalers. |
id |
[Output Only] The unique identifier for the resource. This identifier is defined by the server. |
creationTimestamp |
[Output Only] Creation timestamp in RFC3339 text format. |
name |
Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression |
description |
An optional description of this resource. Provide this property when you create the resource. |
target |
URL of the managed instance group that this autoscaler will scale. This field is required when creating an autoscaler. |
autoscalingPolicy |
The configuration parameters for the autoscaling algorithm. You can define one or more signals for an autoscaler:
,
, and
. If none of these are specified, the default will be to autoscale based on
to
or 60%. |
zone |
[Output Only] URL of the zone where the instance group resides (for autoscalers living in zonal scope). |
region |
[Output Only] URL of the region where the instance group resides (for autoscalers living in regional scope). |
selfLink |
[Output Only] Server-defined URL for the resource. |
status |
[Output Only] The status of the autoscaler configuration. Current set of possible values:
|
statusDetails[] |
[Output Only] Human-readable details about the current state of the autoscaler. Read the documentation for Commonly returned status messages for examples of status messages you might encounter. |
recommendedSize |
[Output Only] Target recommended MIG size (number of instances) computed by autoscaler. Autoscaler calculates the recommended MIG size even when the autoscaling policy mode is different from ON. This field is empty when autoscaler is not connected to an existing managed instance group or autoscaler did not generate its prediction. |
scalingScheduleStatus |
[Output Only] Status information of existing scaling schedules. |
AutoscalingPolicy
Cloud Autoscaler policy.
JSON representation |
---|
{ "minNumReplicas": integer, "maxNumReplicas": integer, "scaleInControl": { object ( |
Fields | |
---|---|
minNumReplicas |
The minimum number of replicas that the autoscaler can scale in to. This cannot be less than 0. If not provided, autoscaler chooses a default value depending on maximum number of instances allowed. |
maxNumReplicas |
The maximum number of instances that the autoscaler can scale out to. This is required when creating or updating an autoscaler. The maximum number of replicas must not be lower than minimal number of replicas. |
scaleInControl |
|
coolDownPeriodSec |
The number of seconds that your application takes to initialize on a VM instance. This is referred to as the initialization period. Specifying an accurate initialization period improves autoscaler decisions. For example, when scaling out, the autoscaler ignores data from VMs that are still initializing because those VMs might not yet represent normal usage of your application. The default initialization period is 60 seconds. Initialization periods might vary because of numerous factors. We recommend that you test how long your application takes to initialize. To do this, create a VM and time your application's startup process. |
cpuUtilization |
Defines the CPU utilization policy that allows the autoscaler to scale based on the average CPU utilization of a managed instance group. |
customMetricUtilizations[] |
Configuration parameters of autoscaling based on a custom metric. |
loadBalancingUtilization |
Configuration parameters of autoscaling based on load balancer. |
mode |
Defines the operating mode for this policy. The following modes are available:
|
scalingSchedules |
Scaling schedules defined for an autoscaler. Multiple schedules can be set on an autoscaler, and they can overlap. During overlapping periods the greatest minRequiredReplicas of all scaling schedules is applied. Up to 128 scaling schedules are allowed. |
ScaleInControl
Configuration that allows for slower scale in so that even if Autoscaler recommends an abrupt scale in of a MIG, it will be throttled as specified by the parameters below.
JSON representation |
---|
{
"maxScaledInReplicas": {
object ( |
Fields | |
---|---|
maxScaledInReplicas |
Maximum allowed number (or %) of VMs that can be deducted from the peak recommendation during the window autoscaler looks at when computing recommendations. Possibly all these VMs can be deleted at once so user service needs to be prepared to lose that many VMs in one step. |
timeWindowSec |
How far back autoscaling looks when computing recommendations to include directives regarding slower scale in, as described above. |
CpuUtilization
CPU utilization policy.
JSON representation |
---|
{
"utilizationTarget": number,
"predictiveMethod": enum ( |
Fields | |
---|---|
utilizationTarget |
The target CPU utilization that the autoscaler maintains. Must be a float value in the range (0, 1]. If not specified, the default is
. If the CPU level is below the target utilization, the autoscaler scales in the number of instances until it reaches the minimum number of instances you specified or until the average CPU of your instances reaches the target utilization. If the average CPU is above the target utilization, the autoscaler scales out until it reaches the maximum number of instances you specified or until the average utilization reaches the target utilization. |
predictiveMethod |
Indicates whether predictive autoscaling based on CPU metric is enabled. Valid values are:
|
PredictiveMethod
Indicates which method of predictive autoscaling is used, if any.
Enums | |
---|---|
NONE |
No predictive method is used. The autoscaler scales the group to meet current demand based on real-time metrics |
OPTIMIZE_AVAILABILITY |
Predictive autoscaling improves availability by monitoring daily and weekly load patterns and scaling out ahead of anticipated demand. |
CustomMetricUtilization
Custom utilization metric policy.
JSON representation |
---|
{
"metric": string,
"filter": string,
"utilizationTargetType": enum ( |
Fields | |
---|---|
metric |
The identifier (type) of the Stackdriver Monitoring metric. The metric cannot have negative values. The metric must have a value type of
or
. |
filter |
A filter string, compatible with a Stackdriver Monitoring filter string for
API call. This filter is used to select a specific TimeSeries for the purpose of autoscaling and to determine whether the metric is exporting per-instance or per-group data. For the filter to be valid for autoscaling purposes, the following rules apply:
Try to provide a filter that is selective enough to pick just one TimeSeries for the autoscaled group or for each of the instances (if you are using
resource type). If multiple TimeSeries are returned upon the query execution, the autoscaler will sum their respective values to obtain its scaling value. |
utilizationTargetType |
Defines how target utilization value is expressed for a Stackdriver Monitoring metric. Either
,
, or
. |
Union field
|
|
utilizationTarget |
The target value of the metric that autoscaler maintains. This must be a positive value. A utilization metric scales number of virtual machines handling requests to increase or decrease proportionally to the metric. For example, a good metric to use as a utilizationTarget is
. The autoscaler works to keep this value constant for each of the instances. |
singleInstanceAssignment |
If scaling is based on a per-group metric value that represents the total amount of work to be done or resource usage, set this value to an amount assigned for a single instance of the scaled group. Autoscaler keeps the number of instances proportional to the value of this metric. The metric itself does not change value due to group resizing. A good metric to use with the target is for example
or a custom metric exporting the total number of requests coming to your instances. A bad example would be a metric exporting an average or median latency, since this value can't include a chunk assignable to a single instance, it could be better used with utilizationTarget instead. |
UtilizationTargetType
Sets the type of utilizationTarget value for a given metric.
Enums | |
---|---|
GAUGE |
Sets the utilization target value for a gauge metric. The autoscaler will collect the average utilization of the virtual machines from the last couple of minutes, and compare the value to the utilization target value to perform autoscaling. |
DELTA_PER_SECOND |
Sets the utilization target value for a cumulative or delta metric, expressed as the rate of growth per second. |
DELTA_PER_MINUTE |
Sets the utilization target value for a cumulative or delta metric, expressed as the rate of growth per minute. |
LoadBalancingUtilization
Configuration parameters of autoscaling based on load balancing.
JSON representation |
---|
{ "utilizationTarget": number } |
Fields | |
---|---|
utilizationTarget |
Fraction of backend capacity utilization (set in HTTP(S) load balancing configuration) that the autoscaler maintains. Must be a positive float value. If not defined, the default is
. |
Mode
Enums | |
---|---|
ON |
Automatically scale the MIG in and out according to the policy. |
OFF |
Do not automatically scale the MIG in or out. The recommendedSize field contains the size of MIG that would be set if the actuation mode was enabled. |
ONLY_UP |
Automatically create VMs according to the policy, but do not scale the MIG in. |
ONLY_SCALE_OUT |
Automatically create VMs according to the policy, but do not scale the MIG in. |
ScalingSchedule
Scaling based on user-defined schedule. The message describes a single scaling schedule. A scaling schedule changes the minimum number of VM instances an autoscaler can recommend, which can trigger scaling out.
JSON representation |
---|
{ "minRequiredReplicas": integer, "schedule": string, "timeZone": string, "durationSec": integer, "disabled": boolean, "description": string } |
Fields | |
---|---|
minRequiredReplicas |
The minimum number of VM instances that the autoscaler will recommend in time intervals starting according to schedule. This field is required. |
schedule |
The start timestamps of time intervals when this scaling schedule is to provide a scaling signal. This field uses the extended cron format (with an optional year field). The expression can describe a single timestamp if the optional year is set, in which case the scaling schedule runs once. The schedule is interpreted with respect to timeZone. This field is required. Note: These timestamps only describe when autoscaler starts providing the scaling signal. The VMs need additional time to become serving. |
timeZone |
The time zone to use when interpreting the schedule. The value of this field must be a time zone name from the tz database: https://en.wikipedia.org/wiki/Tz_database. This field is assigned a default value of "UTC" if left empty. |
durationSec |
The duration of time intervals, in seconds, for which this scaling schedule is to run. The minimum allowed value is 300. This field is required. |
disabled |
A boolean value that specifies whether a scaling schedule can influence autoscaler recommendations. If set to true, then a scaling schedule has no effect. This field is optional, and its value is false by default. |
description |
A description of a scaling schedule. |
Status
Enums | |
---|---|
PENDING |
Autoscaler backend hasn't read new/updated configuration |
DELETING |
Configuration is being deleted |
ACTIVE |
Configuration is acknowledged to be effective |
ERROR |
Configuration has errors. Actionable for users. |
StatusDetails
JSON representation |
---|
{
"message": string,
"type": enum ( |
Fields | |
---|---|
message |
The status message. |
type |
The type of error, warning, or notice returned. Current set of possible values:
|
ErrorType
Note: this enum represents non-actionable warnings and notices in addition to errors.
Enums | |
---|---|
UNKNOWN |
|
ALL_INSTANCES_UNHEALTHY |
All instances in the instance group are unhealthy (not in RUNNING state). |
BACKEND_SERVICE_DOES_NOT_EXIST |
There is no backend service attached to the instance group. |
CAPPED_AT_MAX_NUM_REPLICAS |
Autoscaler recommends a size greater than maxNumReplicas. |
CUSTOM_METRIC_DATA_POINTS_TOO_SPARSE |
The custom metric samples are not exported often enough to be a credible base for autoscaling. |
CUSTOM_METRIC_INVALID |
The custom metric that was specified does not exist or does not have the necessary labels. |
MIN_EQUALS_MAX |
The minNumReplicas is equal to maxNumReplicas. This means the autoscaler cannot add or remove instances from the instance group. |
MISSING_CUSTOM_METRIC_DATA_POINTS |
The autoscaler did not receive any data from the custom metric configured for autoscaling. |
MISSING_LOAD_BALANCING_DATA_POINTS |
The autoscaler is configured to scale based on a load balancing signal but the instance group has not received any requests from the load balancer. |
MODE_OFF |
Autoscaling is turned off. The number of instances in the group won't change automatically. The autoscaling configuration is preserved. |
MODE_ONLY_UP |
Autoscaling is in the "Autoscale only out" mode. Instances in the group will be only added. |
MODE_ONLY_SCALE_OUT |
Autoscaling is in the "Autoscale only scale out" mode. Instances in the group will be only added. |
MORE_THAN_ONE_BACKEND_SERVICE |
The instance group cannot be autoscaled because it has more than one backend service attached to it. |
NOT_ENOUGH_QUOTA_AVAILABLE |
There is insufficient quota for the necessary resources, such as CPU or number of instances. |
REGION_RESOURCE_STOCKOUT |
Showed only for regional autoscalers: there is a resource stockout in the chosen region. |
SCALING_TARGET_DOES_NOT_EXIST |
The target to be scaled does not exist. |
SCHEDULED_INSTANCES_GREATER_THAN_AUTOSCALER_MAX |
For some scaling schedules minRequiredReplicas is greater than maxNumReplicas. Autoscaler always recommends at most maxNumReplicas instances. |
SCHEDULED_INSTANCES_LESS_THAN_AUTOSCALER_MIN |
For some scaling schedules minRequiredReplicas is less than minNumReplicas. Autoscaler always recommends at least minNumReplicas instances. |
UNSUPPORTED_MAX_RATE_LOAD_BALANCING_CONFIGURATION |
Autoscaling does not work with an HTTP/S load balancer that has been configured for maxRate. |
ZONE_RESOURCE_STOCKOUT |
For zonal autoscalers: there is a resource stockout in the chosen zone. For regional autoscalers: in at least one of the zones you're using there is a resource stockout. |
ScalingScheduleStatus
JSON representation |
---|
{
"nextStartTime": string,
"lastStartTime": string,
"state": enum ( |
Fields | |
---|---|
nextStartTime |
[Output Only] The next time the scaling schedule is to become active. Note: this is a timestamp when a schedule is planned to run, but the actual time might be slightly different. The timestamp is in RFC3339 text format. |
lastStartTime |
[Output Only] The last time the scaling schedule became active. Note: this is a timestamp when a schedule actually became active, not when it was planned to do so. The timestamp is in RFC3339 text format. |
state |
[Output Only] The current state of a scaling schedule. |
State
Enums | |
---|---|
ACTIVE |
The current autoscaling recommendation is influenced by this scaling schedule. |
OBSOLETE |
This scaling schedule will never become active again. |
DISABLED |
This scaling schedule has been disabled by the user. |
READY |
The current autoscaling recommendation is not influenced by this scaling schedule. |