Final Update: Wednesday, 16 October 2019 15:13 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/16, 14:15 UTC. Our logs show the incident started on 10/16, 11:00 UTC and that during the 3 hours and 15 minutes that it took to resolve the issue. All customers who created an Azure Monitor metric alert on Redis Cache resources on "Server Load" metric with aggregations Max or Min are experienced alerting failure or may have received false positive alerts.
-
Root Cause: The failure was due to deployment in backend service.
-
Incident Timeline: 3 Hours & 15 minutes - 10/16, 11:00 UTC through 10/16, 14:15 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.
-Anmol
Update: Wednesday, 16 October 2019 13:42 UTC
We continue to investigate issues within Metric Alerts. Root cause is not fully understood at this time. Some customers who created an Azure Monitor metric alert on Redis Cache resources on "Server Load" metric with aggregations Max or Min may still experience issues with Metric Alerts either failing to receive notifications or getting some false alerts. We are working to establish the start time for the issue. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 10/16 18:00 UTC
-Anmol
Initial Update: Wednesday, 16 October 2019 11:23 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers who created an Azure Monitor metric alert on Redis Cache resources on "Server Load" metric with aggregations Max or Min are failing to receive notifications or are getting some false alerts.
- Work Around: None
- Next Update: Before 10/16 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol
