Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(aws-applicationautoscaling): Allow autoscaling with "M out of N" datapoints #17441

Merged
merged 6 commits into from
Dec 14, 2021

Conversation

stephenwiebe
Copy link
Contributor

This PR closes #17433. It adds a datapointsToAlarm property to the StepScalingPolicy construct which allows auto-scaling activities to trigger when only a portion of the data points in the evaluation periods are breaching.

Motivation: Some metrics may have a certain amount of noise/randomness and in these cases it may make more sense to not require that all data points must be breaching for auto-scaling activity to trigger.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link

gitpod-io bot commented Nov 9, 2021

@github-actions github-actions bot added the @aws-cdk/aws-applicationautoscaling Related to AWS Application Auto Scaling label Nov 9, 2021
@stephenwiebe
Copy link
Contributor Author

@comcalvi Any way this could be merged in? There's not much to this change and it'd be nice to have this functionality.

Copy link
Contributor

@comcalvi comcalvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! A few minor changes and this will be ready to be merged.

@stephenwiebe
Copy link
Contributor Author

@comcalvi Ok, I think this should be resolved now.

comcalvi
comcalvi previously approved these changes Dec 6, 2021
Copy link
Contributor

@comcalvi comcalvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stephenwiebe can you add the new property to the relevant section of the readme?

@comcalvi comcalvi dismissed their stale review December 6, 2021 19:53

README needs update

Copy link
Contributor

@comcalvi comcalvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To fix the linter error, could you add the new property and brief of explanation of it to the README?

@mergify mergify bot dismissed comcalvi’s stale review December 8, 2021 07:33

Pull request has been modified.

comcalvi
comcalvi previously approved these changes Dec 9, 2021
Copy link
Contributor

@comcalvi comcalvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for adding this to the readme 😄

@mergify mergify bot dismissed comcalvi’s stale review December 11, 2021 01:31

Pull request has been modified.

@stephenwiebe
Copy link
Contributor Author

@comcalvi What's the next step to get it merged in? I wasn't sure if I needed to merge the master branch back into mine, so I did that but it looks like it might have nullified your review.

@mergify
Copy link
Contributor

mergify bot commented Dec 13, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 0c30c33
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit c21320d into aws:master Dec 14, 2021
@mergify
Copy link
Contributor

mergify bot commented Dec 14, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Feb 21, 2022
… datapoints (aws#17441)

This PR closes aws#17433. It adds a `datapointsToAlarm` property to the `StepScalingPolicy` construct which allows auto-scaling activities to trigger when only a portion of the data points in the evaluation periods are breaching.

Motivation: Some metrics may have a certain amount of noise/randomness and in these cases it may make more sense to not require that all data points must be breaching for auto-scaling activity to trigger.
----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-applicationautoscaling Related to AWS Application Auto Scaling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(aws-applicationautoscaling): Support datapointsToAlarm in StepScalingPolicy
3 participants