I understand we have the feature that "The alert rule sends out a resolved/deactivated message when the alert condition is not met for three consecutive periods to reduce noise in case of flapping conditions.“ referenced by https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-metric-overview#view-and-resolution-of-fired-alerts.
Just for my customer sometimes they have literally thousands of alerts deployed, and this change has broken our alerting mechanisms. Some of these alerts go to a 24/7 helpdesk, and they will phone engineers up and get them out of bed – failing to deactivate the alerts as soon as the issue is resolved will cause our customer significant out of hours support time (and therefore cost) looking into something that does not need to be looked into, because it’s actually already no longer an issue.
And for the workround with Log Alerts, a metric alert would cost $0.138 per month, while a log alert would cost $0.687 per month. That’s a cost increase of $0.549 per alert.
If customer have 1,000 of these, that’s nearly $6,600 per year in increased cost + development time to change all of our alerting, as a result of an unannounced backend change that we didn’t even know was coming, and could not plan for – and that’s not even counting the Log Analytics costs on top of that.
Based on this scenario, may I know do we have any plan to publish the functionality that disable the "hree consecutive periods" feature in the future?