Final Update: Saturday, 29 August 2020 14:15 UTC
We've confirmed that all systems are back to normal with no customer impact as of 08/29, 14:05 UTC. Our logs show the incident started on 08/29, 09:15 UTC and that during the 4 hours 50 minutes that it took to resolve some of customers may experience failures accessing alerts and action rules for the resources. Alerting notifications are not impacted.
-Subhash
We've confirmed that all systems are back to normal with no customer impact as of 08/29, 14:05 UTC. Our logs show the incident started on 08/29, 09:15 UTC and that during the 4 hours 50 minutes that it took to resolve some of customers may experience failures accessing alerts and action rules for the resources. Alerting notifications are not impacted.
- Root Cause: The failure due to one of dependent service miss configuration .
- Incident Timeline: 4 Hours & 50 minutes - 08/29, 09:15 UTC through 08/29, 14:05 UTC
-Subhash
Update: Saturday, 29 August 2020 13:46 UTC
We continue to investigate issues within alerting management. Some customers may experience failures accessing alerts and action rules for resources. Alerting notifications are not impacted. The problem began at 08/29 09:15 AM UTC.
We continue to investigate issues within alerting management. Some customers may experience failures accessing alerts and action rules for resources. Alerting notifications are not impacted. The problem began at 08/29 09:15 AM UTC.
- Work Around: None
- Next Update: Before 08/29 18:00 UTC
Update: Saturday, 29 August 2020 12:02 UTC
We continue to investigate issues within alerting management. Some customers may experience failures accessing alerts and action rules for resources. Alerting notifications are not impacted. The problem began at 08/29 09:15 AM UTC.
- Work Around: None
- Next Update: Before 08/29 16:00 UTC
Updated Aug 30, 2020
Version 4.0
Azure-Monitor-Team
Microsoft
Microsoft
