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

aws_cloudwatch_log_metric_filter - default_value set even when not provided #3131

Closed
marcinwyszynski opened this issue Jan 25, 2018 · 2 comments
Labels
bug Addresses a defect in current functionality.

Comments

@marcinwyszynski
Copy link
Contributor

Hi there,

looks like even when you do not provide default_value in aws_cloudwatch_log_metric_filter, it is set to 0 before being sent.

Terraform Version

0.11.1

Affected Resource(s)

aws_cloudwatch_log_metric_filter

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

resource "aws_cloudwatch_log_metric_filter" "log-throughput" {
  name           = "calculate-log-throughput"
  pattern        = "[marker=EVENTS, events]"
  log_group_name = "/aws/lambda/${lookup(var.paperwatch_config, "function_name")}"

  metric_transformation {
    name      = "EventCount"
    namespace = "Logs/Paperwatch"
    value     = "$$events"
  }
}

Expected Behavior

Default Value in AWS should be None.

Actual Behavior

Default Value in AWS is 0:

cloudwatch_management_console

Steps to Reproduce

Try to create a metric filter with no Default Value.

@bflad bflad added bug Addresses a defect in current functionality. service/cloudwatchlogs labels Jan 25, 2018
@bflad
Copy link
Contributor

bflad commented Jan 25, 2018

Hi @marcinwyszynski! I'm sorry you're having trouble with this and thank you for reporting it. It turns out this is a confirmed bug with an open issue (#2384) and an open PR to fix it (#2759). To consolidate our efforts, I'm going to close this issue in preference of the previously open one, which we will keep updated.

@ghost
Copy link

ghost commented Apr 8, 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 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

No branches or pull requests

2 participants