Skip to content

Using CustomizedMetricSpecification for auto-scaling  #3254

Open
@SlavkaOnline

Description

Does exist the ability to use CustomizedMetricSpecification for auto-scaling now? I can't find an example in docs.
Like here
{ "TargetValue":30.0, "ScaleOutCooldown":120, "ScaleInCooldown":120, "CustomizedMetricSpecification":{ "MetricName":"rate_messages_produced_average_1m", "Namespace":"ECS/CloudWatch/Custom", "Dimensions":[ { "Name":"ClusterName", "Value":"ecs-sarathy-cluster" }, { "Name":"TaskGroup", "Value":"service:PublisherService" } ], "Statistic":"Average" }
https://aws.amazon.com/ru/blogs/containers/autoscaling-amazon-ecs-services-based-on-custom-cloudwatch-and-prometheus-metrics/

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    area/perfopsIssues related to increasing performance of abstractions, or operational configuration.size/MWe should be able to deliver roughly 1 medium issue in a sprint.type/featureIssues that are new feature requests.type/requestIssues that are created by customers.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions