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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support of inputChannelId on sentry_metric_alert #281

Closed
geototti21 opened this issue Feb 17, 2023 · 1 comment
Closed

Add support of inputChannelId on sentry_metric_alert #281

geototti21 opened this issue Feb 17, 2023 · 1 comment

Comments

@geototti21
Copy link
Contributor

馃憢 Hey

I am trying to create a new sentry_metric_alert that has as action a Slack alert.

It is failing with getting the status of the metric alert creation from Sentry took too long, and I believe it is because of the rate limits from Slack. Docs say to also pass the Slack channelID to avoid that.

I can see that inputChannelId is already specified on the go-sentry client, so I believe we need to expose this from the terraform provider as well so it will look like this:

  trigger {
    action {
      type              = "slack"
      target_type       = "specific"
      target_identifier = "#alert-channel"
      # new field needed below
      input_channel_id  = "C0XXXXXXXXX"
      integration_id    = data.sentry_organization_integration.slack.id
    }
    alert_threshold = 300
    label           = "critical"
    threshold_type  = 0
  }

Please let me know what you think. 馃槃

@jianyuan
Copy link
Owner

The input_channel_id is now available in v0.12.0!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants