This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Thursday, 21 April 2022 11:53 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/21, 10:00 UTC. Our logs show the incident started on 04/21, 07:20 UTC and that during the 2 hours & 40 minutes that it took to resolve the issue. Some customers with Application Insights and Log Analytics components in West US 2 region may have experienced intermittent data access, data gaps, incorrect alert activation and missed or delayed alerts.
-Sai Kumar
We've confirmed that all systems are back to normal with no customer impact as of 04/21, 10:00 UTC. Our logs show the incident started on 04/21, 07:20 UTC and that during the 2 hours & 40 minutes that it took to resolve the issue. Some customers with Application Insights and Log Analytics components in West US 2 region may have experienced intermittent data access, data gaps, incorrect alert activation and missed or delayed alerts.
- Root Cause: The failure was due to one of our backend dependency.
- Incident Timeline: 2 Hours & 40 minutes - 04/21, 07:20 UTC through 04/21, 10:00 UTC
-Sai Kumar
Initial Update: Thursday, 21 April 2022 09:24 UTC
We are aware of issues within Log Analytics in West US2 region and are actively investigating. Some customers may experience Data access, delayed or missed Log Search Alerts starting from 4/21 07:20 UTC.
We are aware of issues within Log Analytics in West US2 region and are actively investigating. Some customers may experience Data access, delayed or missed Log Search Alerts starting from 4/21 07:20 UTC.
We are working hard to resolve this issue and apologize for any inconvenience.
-Sai Kumar