Final Update: Monday, 09 August 2021 21:35 UTC
We've confirmed that all systems are back to normal with no customer impact as of 08/09, 20:00 UTC. Our logs show the incident started on 08/09, 17:00 UTC and that during the 3 hours that it took to resolve the issue, A subset of customers may have experienced delayed or missed Log Search Alerts and Metric Alerts on Log Analytics metrics. Customers may also see some data latency.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 08/09, 20:00 UTC. Our logs show the incident started on 08/09, 17:00 UTC and that during the 3 hours that it took to resolve the issue, A subset of customers may have experienced delayed or missed Log Search Alerts and Metric Alerts on Log Analytics metrics. Customers may also see some data latency.
- Root Cause: The failure was due to a bad configuration.
- Incident Timeline: 3 Hours - 08/09, 17:00 UTC through 08/09, 20:00 UTC
-Eric Singleton
Initial Update: Monday, 09 August 2021 19:17 UTC
We are aware of issues within Log Analytics and are actively investigating. A subset of customers may experience delayed or missed Log Search Alerts and metric Alerts on Log analytics metrics. Customers may also see some data latency.
We are aware of issues within Log Analytics and are actively investigating. A subset of customers may experience delayed or missed Log Search Alerts and metric Alerts on Log analytics metrics. Customers may also see some data latency.
- Work Around: none
- Next Update: Before 08/09 23:30 UTC
-Eric Singleton
Updated Aug 09, 2021
Version 2.0