This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 05 November 2020 20:51 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/5, 20:22 UTC. Our logs show the incident started on 11/5, 19:45 UTC and that during the 37 minutes that it took to resolve the issue 166 customers experienced latent log ingestion and possible data gaps.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 11/5, 20:22 UTC. Our logs show the incident started on 11/5, 19:45 UTC and that during the 37 minutes that it took to resolve the issue 166 customers experienced latent log ingestion and possible data gaps.
- Root Cause: The failure was due to backend cache being pushed past an operational threshold. The system was scaled out to mitigate the issue.
- Incident Timeline: 37 minutes - 11/5, 19:45 UTC through 11/5, 20:22 UTC
-Jeff
Initial Update: Thursday, 05 November 2020 20:13 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in East US 2 region may be experiencing intermittent data gaps.
-Jeff
We are aware of issues within Log Analytics and are actively investigating. Some customers in East US 2 region may be experiencing intermittent data gaps.
- Next Update: Before 11/05 22:30 UTC
-Jeff