# Google Cloud Compute V1 API - Module Google::Cloud::Compute::V1::AutoscalerStatusDetails::Type (v3.7.0)

3.7.0 (latest) 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0 3.1.0 3.0.0 2.22.0 2.21.1 2.20.0 2.19.1 2.18.0 2.17.0 2.16.0 2.15.0 2.14.0 2.13.0 2.12.0 2.11.0 2.10.0 2.9.0 2.8.0 2.7.2 2.6.0 2.5.0 2.4.0 2.3.0 2.2.0 2.1.0 2.0.0 1.10.0 1.9.0 1.8.0 1.7.1 1.6.0 1.5.0 1.4.0 1.3.0 1.2.0 1.1.0 1.0.0 0.5.0 Reference documentation and code samples for the Google Cloud Compute V1 API module Google::Cloud::Compute::V1::AutoscalerStatusDetails::Type.

The type of error, warning, or notice returned. Current set of possible
values:


- ALL_INSTANCES_UNHEALTHY (WARNING): All instances in the instance group are unhealthy (not in RUNNING state).
- BACKEND_SERVICE_DOES_NOT_EXIST (ERROR): There is no backend service attached to the instance group.
- CAPPED_AT_MAX_NUM_REPLICAS (WARNING): Autoscaler recommends a size greater than maxNumReplicas.
- CUSTOM_METRIC_DATA_POINTS_TOO_SPARSE (WARNING): The custom metric samples are not exported often enough to be a credible base for autoscaling.
- CUSTOM_METRIC_INVALID (ERROR): The custom metric that was specified does not exist or does not have the necessary labels.
- MIN_EQUALS_MAX (WARNING): The minNumReplicas is equal to maxNumReplicas. This means the autoscaler cannot add or remove instances from the instance group.
- MISSING_CUSTOM_METRIC_DATA_POINTS (WARNING): The autoscaler did not receive any data from the custom metric configured for autoscaling.
- MISSING_LOAD_BALANCING_DATA_POINTS (WARNING): 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 (WARNING): Autoscaling is turned off. The number of instances in the group won't change automatically. The autoscaling configuration is preserved.
- MODE_ONLY_UP (WARNING): Autoscaling is in the "Autoscale only out" mode. The autoscaler can add instances but not remove any.
- MORE_THAN_ONE_BACKEND_SERVICE (ERROR): The instance group cannot be autoscaled because it has more than one backend service attached to it.
- NOT_ENOUGH_QUOTA_AVAILABLE (ERROR): There is insufficient quota for the necessary resources, such as CPU or number of instances.
- REGION_RESOURCE_STOCKOUT (ERROR): Shown only for regional autoscalers: there is a resource stockout in the chosen region.
- SCALING_TARGET_DOES_NOT_EXIST (ERROR): The target to be scaled does not exist.
- UNSUPPORTED_MAX_RATE_LOAD_BALANCING_CONFIGURATION (ERROR): Autoscaling does not work with an HTTP/S load balancer that has been configured for maxRate.
- ZONE_RESOURCE_STOCKOUT (ERROR): 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.

<br />

New values might be added in the future. Some of the values might not be
available in all API versions.

## Constants

### UNDEFINED_TYPE

**value:** 0  
A value indicating that the enum field is not set.

### ALL_INSTANCES_UNHEALTHY

**value:** 404_965_477  
All instances in the instance group are unhealthy (not in RUNNING state).

### BACKEND_SERVICE_DOES_NOT_EXIST

**value:** 191_417_626  
There is no backend service attached to the instance group.

### CAPPED_AT_MAX_NUM_REPLICAS

**value:** 518_617  
Autoscaler recommends a size greater than maxNumReplicas.

### CUSTOM_METRIC_DATA_POINTS_TOO_SPARSE

**value:** 328_964_659  
The custom metric samples are not exported often enough to be a credible
base for autoscaling.

### CUSTOM_METRIC_INVALID

**value:** 204_430_550  
The custom metric that was specified does not exist or does not have the
necessary labels.

### MIN_EQUALS_MAX

**value:** 2_821_361  
The minNumReplicas is equal to maxNumReplicas. This means the autoscaler
cannot add or remove instances from the instance group.

### MISSING_CUSTOM_METRIC_DATA_POINTS

**value:** 94_885_086  
The autoscaler did not receive any data from the custom metric configured
for autoscaling.

### MISSING_LOAD_BALANCING_DATA_POINTS

**value:** 509_858_898  
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

**value:** 164_169_907  
Autoscaling is turned off. The number of instances in the group won't
change automatically. The autoscaling configuration is preserved.

### MODE_ONLY_SCALE_OUT

**value:** 3_840_994  
Autoscaling is in the "Autoscale only scale out" mode.
Instances in the group will be only added.

### MODE_ONLY_UP

**value:** 100_969_842  
Autoscaling is in the "Autoscale only out" mode. Instances in the group
will be only added.

### MORE_THAN_ONE_BACKEND_SERVICE

**value:** 151_922_141  
The instance group cannot be autoscaled because it has more than one
backend service attached to it.

### NOT_ENOUGH_QUOTA_AVAILABLE

**value:** 403_101_631  
There is insufficient quota for the necessary resources, such as CPU or
number of instances.

### REGION_RESOURCE_STOCKOUT

**value:** 528_622_846  
Showed only for regional autoscalers: there is a resource stockout in
the chosen region.

### SCALING_TARGET_DOES_NOT_EXIST

**value:** 122_636_699  
The target to be scaled does not exist.

### SCHEDULED_INSTANCES_GREATER_THAN_AUTOSCALER_MAX

**value:** 29_275_586  
For some scaling schedules minRequiredReplicas is greater than
maxNumReplicas. Autoscaler always recommends at most maxNumReplicas
instances.

### SCHEDULED_INSTANCES_LESS_THAN_AUTOSCALER_MIN

**value:** 398_287_669  
For some scaling schedules minRequiredReplicas is less than
minNumReplicas. Autoscaler always recommends at least minNumReplicas
instances.

### UNKNOWN

**value:**433_141_802

### UNSUPPORTED_MAX_RATE_LOAD_BALANCING_CONFIGURATION

**value:** 330_845_009  
Autoscaling does not work with an HTTP/S load balancer that has been
configured for maxRate.

### ZONE_RESOURCE_STOCKOUT

**value:** 210_200_502  
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.