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.

Sign up for GitHub

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

Jump to bottom

Creating an AWS alarm based on more than one AWS metric. #6955

Closed
ghost opened this issue Dec 20, 2018 · 2 comments
Closed

Creating an AWS alarm based on more than one AWS metric. #6955

ghost opened this issue Dec 20, 2018 · 2 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.

Comments

@ghost
Copy link

ghost commented Dec 20, 2018

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

Current Terraform Version

Terraform v0.11.3
provider.aws v1.52.0

Use-cases

Creating an AWS alarm based on lambda availability. This could for instance be calculated as.

100 - 100 * errors / invocations

Where "errors" and "invocations" are pre defined AWS metrics.

Attempted Solutions

Created the alarm manually using AWS console

Proposal

The terraform resource "aws_cloudwatch_metric_alarm" should support a new argument "metric_expression".
An example value would be "100 - 100 * errors / invocations". For starters we could assume that all metrics in the expression share the same namespace.

References
@ghost ghost mentioned this issue Dec 20, 2018
Closed
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/cloudwatch Issues and PRs that pertain to the cloudwatch service. labels Dec 21, 2018
@bflad
Copy link
Contributor

bflad commented Dec 21, 2018

Hi @jeevesdavid 👋 Thanks for submitting this! It looks like we already have an open issue (#6551) and pull request (#6833) for this functionality, so to consolidate discussions and efforts I'm going to close this issue in preference of those. 👍

@bflad bflad closed this as completed Dec 21, 2018
@ghost
Copy link
Author

ghost commented Apr 1, 2020

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!

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bflad