Final Update: Wednesday, 18 May 2022 07:01 UTC
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 05/18, 05:30 UTC. Our logs show the incident started on 05/17, 19:30 UTC and that during the 10 hours that it took to resolve the issue, some customers using Log Analytics in South Africa North region may have experienced data latency and potential data loss. This may have caused delayed or misfired alerts.
- Root Cause: We determined that a backend service that Log Analytics relies on became unhealthy for a brief period of time causing this issue.
- Incident Timeline: 10 Hours - 05/17, 19:30 UTC through 05/18, 05:30 UTC
-Anmol
Update: Wednesday, 18 May 2022 06:11 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience data latency and potential data loss. This could cause delayed or misfired alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 05/17 ~19:30 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience data latency and potential data loss. This could cause delayed or misfired alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 05/17 ~19:30 UTC. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 05/18 09:30 UTC
Update: Wednesday, 18 May 2022 03:00 UTC
We continue to investigate issues within Log Analytics in South Africa North. Root cause is not fully understood at this time. Some customers continue to experience data latency and potential data loss. This could cause delayed or misfired alerts.
We continue to investigate issues within Log Analytics in South Africa North. Root cause is not fully understood at this time. Some customers continue to experience data latency and potential data loss. This could cause delayed or misfired alerts.
- Work Around: none
- Next Update: Before 05/18 05:00 UTC
Updated May 18, 2022
Version 3.0