As of today, our ASG submodule is supporting target tracking scaling policies and by default the estimated_instance_warmup timer is 300sec which is too low comparing the time required for a VM-Series to be fully operational. It may cause too many scale-out events if the VM-Series is not yet publishing its metrics.
Describe the solution you'd like
We should allow the end user to configure estimated_instance_warmup under aws_autoscalingplans_scaling_plan > target_tracking_configuration to allow input a value around 15-20 min (AVG time for a VM to be fully bootstrapped)
Is your feature request related to a problem?
As of today, our ASG submodule is supporting target tracking scaling policies and by default the estimated_instance_warmup timer is 300sec which is too low comparing the time required for a VM-Series to be fully operational. It may cause too many scale-out events if the VM-Series is not yet publishing its metrics.
Describe the solution you'd like
We should allow the end user to configure estimated_instance_warmup under aws_autoscalingplans_scaling_plan > target_tracking_configuration to allow input a value around 15-20 min (AVG time for a VM to be fully bootstrapped)
Describe alternatives you've considered.
No response
Additional context
No response