Final Update: Wednesday, 16 February 2022 18:25 UTC
We've confirmed that all systems are back to normal as of 02/16 17:55 UTC. Our logs show the incident started on 02/16, 13:07 UTC and that during this duration that it took to resolve the issue customers in West Europe region might have experienced data latency and missed alerts.
-chandar
We've confirmed that all systems are back to normal as of 02/16 17:55 UTC. Our logs show the incident started on 02/16, 13:07 UTC and that during this duration that it took to resolve the issue customers in West Europe region might have experienced data latency and missed alerts.
- Root Cause: We have found that a backend service that Log Analytics is reliant on has become unhealthy causing the latencies.
- Incident Timeline: 02/16, 13:07 UTC through 02/16 17:55 UTC
-chandar
Update: Wednesday, 16 February 2022 17:00 UTC
We have found that a backend service that Log Analytics is reliant, has become unhealthy causing ingestion latencies. We performed a repair of a backend node to mitigate the issue and we have started to see recovery. To expedite the recovery, we have also scaled out the number of instances of one of our backend services.
- Work Around:
- Next Update: Before 02/16 19:00 UTC
Updated Feb 16, 2022
Version 2.0