This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Thursday, 09 December 2021 09:24 UTC
We've confirmed that all systems are back to normal with no customer impact as of 12/09, 08:46 UTC. Our logs show the incident started on 12/09, 05:08 UTC and that during the 3 hours & 38 minutes that it took to resolve the issue, customers may have experienced intermittent log data gaps and incorrect alert activation in Japan East region.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 12/09, 08:46 UTC. Our logs show the incident started on 12/09, 05:08 UTC and that during the 3 hours & 38 minutes that it took to resolve the issue, customers may have experienced intermittent log data gaps and incorrect alert activation in Japan East region.
- Root Cause: The failure was due to one of the backend service became unhealthy.
- Incident Timeline: 3 Hours & 38 minutes - 12/09, 05:08 UTC through 12/09, 08:46 UTC
-Srikanth
Initial Update: Thursday, 09 December 2021 07:54 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience intermittent log data gaps and incorrect alert activation starting from 12/09, 05:08 UTC
-Sandeep
We are aware of issues within Application Insights and are actively investigating. Some customers may experience intermittent log data gaps and incorrect alert activation starting from 12/09, 05:08 UTC
- Work Around: None
- Next Update: Before 12/09 09:00 UTC
-Sandeep