This article is contributed. See the original author and article here.

Final Update: Wednesday, 14 October 2020 22:36 UTC

We’ve confirmed that all systems are back to normal with no customer impact as of 10/14, 22:35 UTC. Our logs show the incident started on 10/14, 20:53 UTC and that during the one hour and 43 minutes that it took to resolve the issue 22% of customers experienced query failures and/or log search alerts failures (alerts firing incorrectly, not firing, or delayed).
  • Root Cause: An unexpected increase in traffic to Log Analytics in this region caused a back end component to fail. When the component was restarted, the issue was mitigated.
  • Incident Timeline: 1 Hours & 43 minutes – 10/14, 20:53 UTC through 10/14, 22:35 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Wednesday, 14 October 2020 22:01 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Log Search Alerts failures (failed alerts, delayed alerts, or incorrect alerts) as well as errors querying data for Log Analytics workspaces.
  • Next Update: Before 10/14 23:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack Cantwell

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

%d bloggers like this: