Final Update: Thursday, 01 October 2020 02:06 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/01, 02:09 UTC. Our logs show the incident started on 09/30,19:50 UTC and that during the 6 hours and 19 minutes that it took to resolve the issue some of the customers in West Central US, Australia South East regions may have experienced issues with Data Latency in AzureDiagnostics and AzureMetrics which may cause misfiring of alerts.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 10/01, 02:09 UTC. Our logs show the incident started on 09/30,19:50 UTC and that during the 6 hours and 19 minutes that it took to resolve the issue some of the customers in West Central US, Australia South East regions may have experienced issues with Data Latency in AzureDiagnostics and AzureMetrics which may cause misfiring of alerts.
- Root Cause: The failure was due to an issue with the recent deployment.
- Incident Timeline: 6 Hours & 19 minutes - 09/30, 19:50 UTC through 10/01, 02:09 UTC
-Jayadev
Initial Update: Thursday, 01 October 2020 01:47 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in West Central US, Australia south East regions may experience issues with Data Latency in AzureDiagnostics and AzureMetrics which may cause misfiring of alerts.
-Vincent
We are aware of issues within Log Analytics and are actively investigating. Some customers in West Central US, Australia south East regions may experience issues with Data Latency in AzureDiagnostics and AzureMetrics which may cause misfiring of alerts.
- Work Around: none
- Next Update: Before 10/01 04:00 UTC
-Vincent
Updated Oct 01, 2020
Version 4.0