This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 24 January 2020 07:36 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/24, 07:20 UTC. Our logs show the incident started on 01/23, 23:55 UTC and that during the 7 hours and 25 minutes that it took to resolve the issue ~80% of customers in West US2 may have experienced issues while querying data, delayed or missing alerts.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 01/24, 07:20 UTC. Our logs show the incident started on 01/23, 23:55 UTC and that during the 7 hours and 25 minutes that it took to resolve the issue ~80% of customers in West US2 may have experienced issues while querying data, delayed or missing alerts.
- Root Cause: The failure was due to one of the backend service getting overloaded. The backend service was unable to scale out due to ongoing OS Patching.
- Incident Timeline: 7 Hours & 25 minutes - 01/23, 23:55 UTC through 01/24, 07:20 UTC
-Anmol
Update: Friday, 24 January 2020 06:58 UTC
We still continue to investigate issues within Azure monitor. Some customers continue to experience query failures, missing or delayed alerts. Initial findings indicate that the problem began at 01/23 23:55 UTC. We currently have no estimate for resolution.
We still continue to investigate issues within Azure monitor. Some customers continue to experience query failures, missing or delayed alerts. Initial findings indicate that the problem began at 01/23 23:55 UTC. We currently have no estimate for resolution.
- Work Around:
- Next Update: Before 01/24 10:00 UTC
Update: Friday, 24 January 2020 04:05 UTC
We continue to investigate issues within Azure monitor. We are working on establishing the root cause, and as per our preliminary investigation the root cause is due to one of the backend services getting overloaded. Some customers continue to experience query failures, missing or delayed alerts. Initial findings indicate that the problem began at 01/23 23:55 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Azure monitor. We are working on establishing the root cause, and as per our preliminary investigation the root cause is due to one of the backend services getting overloaded. Some customers continue to experience query failures, missing or delayed alerts. Initial findings indicate that the problem began at 01/23 23:55 UTC. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 01/24 07:30 UTC
Initial Update: Friday, 24 January 2020 01:51 UTC
We are aware of issues within Log Analytics and Log search alerts and are actively investigating. Some customers in West US2 may experience issues while querying data, delayed or missing alerts.
-Anupama
We are aware of issues within Log Analytics and Log search alerts and are actively investigating. Some customers in West US2 may experience issues while querying data, delayed or missing alerts.
- Work Around: None
- Next Update: Before 01/24 04:00 UTC
-Anupama