GCP Compute Engine Autoscaler

Google Cloud Platform (GCP) Compute Engine Autoscalers are used to automatically add or delete instances from a managed instance group according to your defined autoscaling policy.

You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.

Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Detail View

To display the detail view of a GCP Compute Engine Autoscaler:

Navigate to the Observe page.
Under Compute, click GCP Autoscalers.
The list view now displays.
From the list, click an entity Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Compute Engine Autoscaler. See Google Cloud metrics.

Display Name	Source Metric	Description
Capacity (%)	`capacity`	The utilization target multiplied by number of serving VMs.
Utilization (%)	`current_utilization`	The sum of the utilization of a specified metric for all serving VMs.
Recommended Size (Count)	`scheduled_size`	The minimum number of VMs that the autoscaler recommends according to the scaling schedule.

Properties (Attributes)

Cisco Cloud Observability displays the following properties for GCP Compute Engine Autoscaler.

Display Name	Source Property Name	Description
ID	-	The ID of the autoscaler account, trimmed from the `selfLink`.
Name	-	The name of the autoscaler, trimmed from the `selfLink`.
Numeric ID	`id`	The numeric ID of the autoscaler.
Self Link	`selfLink`	The autoscaler `selfLink`.
Project ID	-	The ID of the GCP project.
Region	`region`	The region of the autoscaler.
Zone	`zone`	The zone of the autoscaler.
Status	`status`	The status of the autoscaler configuration. Current set of possible values: `PENDING`: The autoscaler backend hasn't read the new/updated configuration. `DELETING`: The configuration is being deleted. `ACTIVE`: The configuration is acknowledged to be effective. `ERROR`: The configuration has errors.
Target	`target`	The URL of the managed instance group (MIG) that this autoscaler will scale.
Created Time	`creationTimestamp`	The creation timestamp of the autoscaler.
Policy Mode	`autoscalingPolicy.mode`	Defines the operating mode for this policy. The following modes are available: `OFF`: Disables the autoscaler. `ONLY_SCALE_OUT`: Restricts the autoscaler to add VM instances only. `ON`: Enables all autoscaler activities according to its policy.
Actual Number of Replicas	`autoscalingPolicy.scaleInControl.maxScaledInReplicas.calculated`	The absolute value of VM instances calculated based on the specific mode: `fixed`: The value is equal to the fixed value. `percent`: The value is `percent/100 * targetSize`.
Minimum Number of Replicas	`autoscalingPolicy.minNumReplicas`	The minimum number of replicas that the autoscaler can scale in to.
Maximum Number of Replicas	`autoscalingPolicy.maxNumReplicas`	The maximum number of instances that the autoscaler can scale out to.
Recommended Number of Replicas	`recommendedSize`	The target recommended MIG size (number of instances) computed by the autoscaler.
Recommendation Time Window (s)	`autoscalingPolicy.scaleInControl.timeWindowSec`	Specifies how far back autoscaling looks when computing recommendations to include directives regarding slower scale in, as described above.
Cooldown Period (s)	`autoscalingPolicy.coolDownPeriodSec`	The number of seconds that your application takes to initialize on a VM instance. This is referred to as the initialization period.
CPU Utilization Target	`autoscalingPolicy.cpuUtilization.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 0.6.
CPU Utilization Predictive Method	`autoscalingPolicy.cpuUtilization.predictiveMethod`	Specifies whether predictive autoscaling based on CPU metric is enabled. Valid values: `NONE` (default) `OPTIMIZE_AVAILABILITY`
Load Balancer Utilization Target	`autoscalingPolicy.loadBalancingUtilization.utilizationTarget`	The 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 0.8.

Retention and Purge Time-To-Live (TTL)

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.