This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 15 February 2022 16:53 UTC
We've confirmed that all systems are back to normal as of 02/15, 16:45 UTC. Our logs show the incident started on 02/15, 13:00 UTC and that during the time it took to resolve the issue Azure Log Analytics customers experienced gaps in data sent between 13:00 UTC and 15:00 UTC
-chandar
We've confirmed that all systems are back to normal as of 02/15, 16:45 UTC. Our logs show the incident started on 02/15, 13:00 UTC and that during the time it took to resolve the issue Azure Log Analytics customers experienced gaps in data sent between 13:00 UTC and 15:00 UTC
- Root Cause: The failure was due to compute infrastructure that stopped the service from functioning.
- Incident Timeline: 02/15, 13:00 UTC through 02/15, 16:45 UTC
-chandar
Update: Tuesday, 15 February 2022 16:30 UTC
Due to backend infrastructure failure, customers in South UK region may experience data gaps for data sent to Azure Log Analytics between 02/15 1:00 PM UTC - 3:00 PM UTC, and we estimate 2 hours before the data gaps are addressed.
Due to backend infrastructure failure, customers in South UK region may experience data gaps for data sent to Azure Log Analytics between 02/15 1:00 PM UTC - 3:00 PM UTC, and we estimate 2 hours before the data gaps are addressed.
- Work Around: none.
- Next Update: Before 02/15 18:30 UTC