Experiencing Alerting failure for Azure Monitor in Azure China – 04/13 – Resolved

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Final Update: Tuesday, 14 April 2020 00:37 UTC

We've confirmed that all systems are back to normal with no customer impact as of 4/14, 12:23 UTC. Our logs show the incident started on 4/13, 21:25 UTC and that during the ~3 hours that it took to resolve the issue customers in Azure China region experienced delayed or missed alerts and data access issues
  • Root Cause: The failure was due to a backend service becoming unresponsive. 
  • Incident Timeline: 3 Hours - 4/13, 21:25 UTC through 4/14, 12:23 UTC
We understand that customers rely on Log Search Alerts and Log analytics as a critical service and apologize for any impact this incident caused.

-Anupama

Update: Tuesday, 14 April 2020 00:24 UTC

We continue to investigate issues within Log Search Alerts and Log analytics. Root cause is not fully understood at this time.
Some customers in Azure China region continue to experience delayed or missed alerts and data access issues. Initial findings indicate that the problem began at 4/13 ~21:25 UTC. We currently have no estimate for resolution.
  • Work Around:
  • Next Update: Before 04/14 02:30 UTC
-Anupama

Initial Update: Monday, 13 April 2020 22:48 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience delayed or missed log search alerts in China Gov region.
  • Work Around: None
  • Next Update: Before 04/14 02:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anupama

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.