aws_cloudwatch_metric_alarm period issue

[hashibot]

This issue was originally opened by @bryanheo as hashicorp/terraform#15543. It was migrated here as a result of the provider split. The original body of the issue is below.

---

PROVIDER ISSUES

PLEASE NOTE: Terraform has split out the builtin Providers into their own repositories. For any Provider issues, please open all issues and pull requests in the corresponding repository. An index of supported Providers can be found here:

• https://github.com/terraform-providers

All other issues (that appear to affect multiple or all providers) may be an issue with Terraform's core, and should be opened here.

---

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
0.9.11

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

resource "aws_cloudwatch_metric_alarm" "asg_group_terminating_instances" {
alarm_name = "asgGroupTerminatingInstances-001"
comparison_operator = "GreaterThanOrEqualToThreshold"
evaluation_periods = "2"
metric_name = "GroupTerminatingInstances"
namespace = "AWS/AutoScaling"
period = "300"
statistic = "Maximum"
threshold = "1"

dimensions {
AutoScalingGroupName = "${aws_autoscaling_group.default.name}"
}

lifecycle {
create_before_destroy = true
}
}

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

What should have happened?
GroupTerminatingInstances >= 1 for 5 minutes

Actual Behavior

What actually happened?
GroupTerminatingInstances >= 1 for 10 minutes

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
   N/A

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
N/A

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Make aws_iam_policy_attachment warning less opaque #1234

[stack72]

Hi @bryanheo

So I believe this is correct. The threshold will be the number of consecutive evaluation_periods * number of periods

So in this specific code 2 * 300seconds == 10 minutes

I was able to verify that this is also what the AWS UI does as well - were you expecting something different?

Paul

[bryanheo]

Thank you for the clarification

[tombuildsstuff]

Hey @bryanheo

Reading through this I believe this issue has been resolved - as such I'm going to close this issue for the moment. However please feel free to reopen it if there's still an issue here and we'll take another look :)

Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!