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

Support for window_size/frequency at criteria/dynamic_criteria levels for azurerm_monitor_metric_alert #27556

Closed
1 task done
zalex-1 opened this issue Oct 2, 2024 · 1 comment

Comments

@zalex-1
Copy link

zalex-1 commented Oct 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.

Description

When creating Azure Alert Rule in Azure Portal, I'm able to define multiple Conditions, each with its own frequency and window: https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-metric-multiple-time-series-single-rule

However in Terraform, I cannot create Criteria with its own frequency/window_size: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/monitor_metric_alert

New or Affected Resource(s)/Data Source(s)

azurerm_monitor_metric_alert

Potential Terraform Configuration

No response

References

No response

@zalex-1
Copy link
Author

zalex-1 commented Oct 3, 2024

I did not see this message in Azure Portal initially: "The selected frequency and period must match across all conditions. If different values are selected across conditions, the largest one will be used."

For Terraform works fine. My apologies.

@zalex-1 zalex-1 closed this as completed Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant