This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 16 November 2020 02:09 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/16, 01:20 UTC. Our logs show the incident started on 11/16, 00:15 UTC and that during the 1 hour and 5 minutes that it took to resolve the issue some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 11/16, 01:20 UTC. Our logs show the incident started on 11/16, 00:15 UTC and that during the 1 hour and 5 minutes that it took to resolve the issue some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe.
- Root Cause: The failure was due to an issue with one of our backend services.
- Incident Timeline: 1 Hours & 5 minutes - 11/16, 00:15 UTC through 11/16, 01:20 UTC
-Eric Singleton
Initial Update: Monday, 16 November 2020 01:06 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe.
-Eric Singleton
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe.
- Work Around: None
- Next Update: Before 11/16 03:30 UTC
-Eric Singleton