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

Feature request for Suppressing the alerts after certain time in azurerm_monitor_scheduled_query_rules_alert #6842

Closed
PalPalo opened this issue May 10, 2020 · 3 comments

Comments

@PalPalo
Copy link

PalPalo commented May 10, 2020

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

New or Affected Resource(s)

  • azurerm_monitor_scheduled_query_rules_alert

Potential Terraform Configuration

*azurerm_monitor_scheduled_query_rules_alert

References

https://www.terraform.io/docs/providers/azurerm/r/monitor_scheduled_query_rules_alert.html

  • #0000
@mcdafydd
Copy link
Contributor

Hello,

I think this particular form of suppression is already supported in the resource. In the Microsoft example, they refer to suppression within a scheduled query rule like this:

"throttlingInMin": "[variables('alertActions').SuppressTimeinMin]",

This should be supported by the existing resource:

throttling - (Optional) Time (in minutes) for which Alerts should be throttled or suppressed. Values must be between 0 and 10000 (inclusive).

Additional suppression support will come from Action Rules, and it looks like a PR (#6563) has already been submitted for that (yay!).

@favoretti
Copy link
Collaborator

Since this issue seems to have been addressed in the latest versions of the provider (or a valid workaround was provided) - I'm going to close it. Please open a new updated bug report if this is still relevant. Thank you.

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants